Skip to content

add module entry point for webpack v2 #3788 #3789

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

Closed

Conversation

mrtnbroder
Copy link

No description provided.

@taion
Copy link
Contributor

taion commented Sep 5, 2016

Ref my note in #3788 (comment). There's definitely an (odd, unexpected) cost to this. I'm not sure this is a good idea.

@timdorr
Copy link
Member

timdorr commented Sep 9, 2016

That seems like more of a webpack and babel problem. Given that webpack 2 isn't out of beta, not lot of people are going to be running into the issue just yet. Those that are would be accepting the cost of running beta software: rough edges like these.

I wouldn't want to just hand wave over the issue, but good saved reply should take care of the workload on us.

@timdorr
Copy link
Member

timdorr commented Sep 28, 2016

I'm going to close this out since it's against master. It should be only on the v3 branch, which already has a jsnext:main

@timdorr timdorr closed this Sep 28, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants