-
Notifications
You must be signed in to change notification settings - Fork 938
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
Publish UMD bundle for use in browser #545
Comments
No. Please use webpack or similar. |
Anyone who excludes the node_modules from the build process must change their config to include debug. Or create an alias. In any case, this is not the most practical thing. |
Please see sindresorhus/ama#446 (comment). Using babel is the future at this point. Please modernize your build steps to use new versions of Version 4 was breaking. That's why it was a major version bump. A quick search would have shown you that @bertho-zero. Either you're mis-using ranges or you're using
There is nothing actionable here. |
With the rise of unpkg as a CDN for published bundles, would it be acceptable to publish a browser consumable bundle with the NPM package?
The text was updated successfully, but these errors were encountered: