Closed aral closed 1 month ago
❯ ls build/lib/index.js
build/lib/index.js
❯ cat build/package.json| grep main
"main": "./lib/index.js",
We stil ship this file... if someone else has any more specific details on this failure...
This appears to be due to installing highlight.js from the GitHub repository as opposed to from the npm registry
Because lib
is not built in that context, importing lib
does not work
I'm confident it will work in future npm releases of highlight.js :)
Running npm run build
as part of the prepare
npm script would probably allow installing from GitHub directly if that's something you're keen on supporting
This appears to be due to installing highlight.js from the GitHub repository as opposed to from the npm registry
Yes, our GitHub repo here is the raw (unbuilt) source, it's not meant to be used via npm, etc.
You might have better luck with: https://github.com/highlightjs/cdn-release
Describe the issue/behavior that seems buggy
It looks like something changed in main that’s breaking the markdown-it-highlightjs plugin when upgraded to it from the version it is currently using (11.5.1)
Specifically, tests pass before the upgrade but when running the tests after an upgrade, I’m seeing:
(Full stack trace at end.)
Sample Code or Instructions to Reproduce
git clone https://github.com/valeriangalliat/markdown-it-highlightjs.git
cd markdown-it-highlightjs.git
npm i
npm run test
and note all tests passingnpm i
npm run test
Expected behavior
Since 11.5.1 →11.9.0 (version in main) is a semver minor update, I’d expect all tests to still pass.
The issue does not exist in the release version of 11.9.0, where all tests pass, so this is either a regression or a breaking change in main.
Actual behavior
Tests fail with error message mentioned above and with full stack trace as provided below.
Additional context
Full stack trace: