We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I noticed that #388 changed build/vega-datasets.min.js to be an IIFE:
vega-datasets/rollup.config.js
Lines 40 to 46 in b2c5de0
Whereas build/vega-datasets.js is still a UMD:
Lines 34 to 39 in b2c5de0
The problem is that require("vega-datasets") on Observable will use your unpkg/jsdelivr entry point which points to the IIFE, and thus errors:
require("vega-datasets")
vega-datasets/package.json
Lines 8 to 9 in b2c5de0
You can see it breaking here:
https://observablehq.com/@vega/vega-lite-input-binding
If you want to drop UMD support, we could fix that notebook (and presumably others) by using ES import instead of require:
world = (await import('vega-datasets')).default['world-110m.json'].url
But if you are supporting IIFE, maybe it’s worth continuing to support UMD for backwards compatibility?
The text was updated successfully, but these errors were encountered:
Thanks for the issue. I'll switch back to umd.
Sorry, something went wrong.
fix: switch back to UMD bundles
6152f95
fixes #391
🚀 Issue was released in v2.5.2-next.0 🚀
v2.5.2-next.0
Thanks for working on these issues Dominik!
Successfully merging a pull request may close this issue.
I noticed that #388 changed build/vega-datasets.min.js to be an IIFE:
vega-datasets/rollup.config.js
Lines 40 to 46 in b2c5de0
Whereas build/vega-datasets.js is still a UMD:
vega-datasets/rollup.config.js
Lines 34 to 39 in b2c5de0
The problem is that
require("vega-datasets")
on Observable will use your unpkg/jsdelivr entry point which points to the IIFE, and thus errors:vega-datasets/package.json
Lines 8 to 9 in b2c5de0
You can see it breaking here:
https://observablehq.com/@vega/vega-lite-input-binding
If you want to drop UMD support, we could fix that notebook (and presumably others) by using ES import instead of require:
But if you are supporting IIFE, maybe it’s worth continuing to support UMD for backwards compatibility?
The text was updated successfully, but these errors were encountered: