-
Notifications
You must be signed in to change notification settings - Fork 195
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 jsonld.js with rollup #355
Comments
Yes, I have also issues with rollup. I'm trying to use These are my errors when building, using the library like
Using the minified version from |
I've just updated the example repo to jsonld 3.x and rollup 2.x. Minified no-op bundle size is still at 230kb |
Current focus is on 1.1 and related features. After that I hope to see the code switch over to ESM style and do some related cleanups. If using tree shaking tools then that should help with the size before even looking at other optimizations. |
Closing as a duplicate of #399. |
Nice to see some progress, thanks! |
I've updated my example repo now (newer versions, not using the minified bundle): https://github.com/lazka/jsonld-rollup-test We are down from 215kb to 115kb minified, which is a nice improvements. |
Hey, more of a support question:
I'm trying to use jsonld.js with rollup for browser bundling and I was wondering if anyone has a working setup for it already or can give some hints on how to improve things (or can recommend an alternative library for parsing jsonld)
I can just import the minified version on npm, but that doesn't give me named exports and no treeshaking and jsonld.js is too large as is.
I have a minimal working rollup+jsonld setup here if someone wants to give it a try: https://github.com/lazka/jsonld-rollup-test
The text was updated successfully, but these errors were encountered: