You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> *[Click here to open the sample on flems.io](https://flems.io/mithril@main#0=N4IgZglgNgpgziAXAbVAOwIYFsZJAOgAsAXLKEAGhAGMB7NYmBvEAXwvW10QICsEqdBk2J4s+LLQCuDABQATWtSk4G+AEa15ATwoACYAB00e03oBuEGAHdEesDOrEI9WQEoDxs970AnGMRSviZYsgDkhACMYfphACq+2no4etLEYW5eZqzGrG6UIHAwsE4uaAg8ACyIAExsHCCYOHj41HACNPSMzDxsALqsQA)*
The git branch name next has been changed to main, but next is still used as the npm tag.
Activity
dead-claudia commentedon Sep 12, 2025
Where is this link?
boustanihani commentedon Sep 12, 2025
On the main site: https://mithril.js.org/
imanabu commentedon Sep 13, 2025
The original poster seems right and issue is reproducible.
I click the link.
And there appears to be some blocked content for this to be able to run.
imanabu commentedon Sep 13, 2025
How can I help with this?
kfule commentedon Sep 13, 2025
Perhaps, the following line will need to be corrected.
docs/docs/index.md
Line 87 in 3d3493e
The git branch name
nexthas been changed tomain, butnextis still used as the npm tag.dead-claudia commentedon Sep 14, 2025
I elected to have it use the current version. It shouldn't be following unstable tags, but the latest version.
Anyways, should be fixed shortly, if the deployment hasn't already completed. (GitHub Pages deployments are almost instant in my experience.)
boustanihani commentedon Sep 24, 2025
The issue still exists..
Replace the "[version]" in the body of the markdown, fix MithrilJS#37
Replace the "[version]" in the body of the markdown, fix #37 (#39)
dead-claudia commentedon Oct 5, 2025
@boustanihani #39 should fix it now
boustanihani commentedon Oct 5, 2025
Thanks, its working :)