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
Stop exposing src directory on npm #6170
Comments
This would also be a good time to simplify the browser/node switching in our codebase using the trick in https://nolanlawson.com/2017/01/09/how-to-write-a-javascript-package-for-both-node-and-the-browser/ |
nolanlawson
added a commit
that referenced
this issue
Jan 24, 2017
nolanlawson
added a commit
that referenced
this issue
Jan 25, 2017
nolanlawson
added a commit
that referenced
this issue
Jan 25, 2017
nolanlawson
added a commit
that referenced
this issue
Jan 25, 2017
nolanlawson
added a commit
that referenced
this issue
Jan 26, 2017
daleharvey
pushed a commit
that referenced
this issue
Jan 31, 2017
Closed
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our src is starting to contain more and more custom code that Rollup alters on the fly. I'd be more comfortable with building explicit ES module bundles on the same way we build CJS bundles.
The text was updated successfully, but these errors were encountered: