11.0.0-beta1 is available for testing.
See original GitHub issueHow to get it:
npm install highlight.js@11.0.0-beta1
- build it from source (fetch the
11.0.0-beta1
tag) - fetch it via CDN.
Please open a new issue if you have bugs or issues to report.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:29 (16 by maintainers)
Top Results From Across the Web
BuddyPress 11.0.0-beta1
0-beta1 is available for testing ! Please note the plugin is still in development, so we recommend running this beta release on a...
Read more >Asterisk 11.0.0-beta1 Now Available! ⋆ Asterisk
Asterisk 11.0.0-beta1 Now Available! ... All interested users of Asterisk are encouraged to participate in the Asterisk 11 testing process.
Read more >org.eclipse.jetty:jetty-client 11.0.0.beta1 vulnerabilities | Snyk
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free. Fix for free. Vulnerability ...
Read more >[boost] [1.50.0] Beta 1 release candidates available for testing
Release candidate files for 1.50.0 beta 1 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download
Read more >beta - BP Dev Updates
We need your help, please contribute to BuddyPress 11.0.0 beta testing starting with this first ... BuddyPress 10.0.0-beta1 is available for your tests!...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
What is the “it” this is referring to?
Huh, I’m not following? Which files and what do you mean “upgrade to ESM”?
Well the v11 release isn’t necessarily going to happen until post Node v10 sunsetting, so there is still time for the situation to improve.
Indeed, but we’re not shipping two separate packages and I’m not a fan of this fervor to immediately “switch” the whole ecosystem to ESM, so that means we either ignore ESM for another release cycle or ship dual… and shipping dual seemed the better of those two choices to me.
Ah, I hadn’t even considered that that because I’m not really interested in adding TS to our build pipeline (in my prior experience it’s ridiculous slow). Something to consider for the future perhaps. I just got the ambient module stuff working and not interested in burning more time on this now.
I will save all those references for future reference though.