-
Notifications
You must be signed in to change notification settings - Fork 34
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
jsnext:main should not point to completely untranspiled code #22
Comments
+1 |
1 similar comment
+1 |
Fixed by #23 |
Unfortunately, this appears to be broken in a different way now. The exports.default = ExtendableError;
module.exports = exports['default']; That is commonJS module syntax. The file that export default ExtendableError; Should we reopen the issue and track that here, or should I open a new issue for it? |
Closed
See #25 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the Rollup docs:
Libraries that expose an ES6 module build should transpile the code in a way that makes it ES5-compatible, but leaves "import" and "export" statements intact. The reason is that we can't transpile all node_modules for a project, nor would we know what babel config to use on each of them. See this conversation for more discussion. Pointing "jsnext:main" to a file with the "class" keyword is breaking our build.
The text was updated successfully, but these errors were encountered: