-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using HLJS as a package dependency #3597
Labels
Comments
The ESM builds included in the main npm package are intended for use with the Node.js runtime, NOT to be compiled with build tools for bundling for the web... you may want to check out our CDN ESM builds instead: https://www.npmjs.com/package/@highlightjs/cdn-assets which are "pure" ESM. I have no idea if that's your problem or not, just a thought. |
Closing for inactivity, please response if you need further help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue/behavior that seems buggy
We have a UI component library written in Svelte and one of the components utilises HLJS and it all works very nicely. However, when we pack our library and include HLJS in package.json:
"dependencies": { "highlight.js": "^11.6.0" }
Our end users get:
Indirectly exported binding name 'default' cannot be resolved by star export entries.
I see this is referenced in the discussion #3527 but I can't tell from that discussion what I need to do to resolve it.
I'm just wondering if there is any docs/other project links/any information on how we can properly include HLJS in our exported package so that it works for our end users ?
Cheers,
Nik
The text was updated successfully, but these errors were encountered: