-
Notifications
You must be signed in to change notification settings - Fork 331
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
UMD build undefined when no default export #411
Comments
I've created a Webpack feature request for this, as it would be nice for everyone if Faiing that, alternative courses of action are:
It's not ideal, but in the meantime you should be able to use |
Thanks for the comments on this. I found myself in a similar situation and used the However, FWIW, from my perspective, a |
This issue is a:
I have a vanilla JS web component that defines named exports in
src/index.js
like such:This leads to the umd global variable being undefined.
If changing above to a default export
things work for umd, and the umd variable is an object as expected
{ a, b, c }
I've read that nwb recently dropped the need to address default exports via
.default
.Perhaps that change has to be skipped if named exports are present?
Is the version of
nwb
you're using installed globally or locally?global
Which versions of Node.js, npm and nwb are you using (if using it globally)?
node v8.9.1, yarn@1.3.2, nwb@0.20.0
The text was updated successfully, but these errors were encountered: