-
Notifications
You must be signed in to change notification settings - Fork 33
Conversation
probably worth deprecating this module now. |
@graingert absolutely not, it's still crucial for webpack 1 usage. |
@ljharb but webpack 1 is old and broken now. |
Is it not irrelevant whether one considers this repo obsolete or not? This pull request is just about notifying users that they don't need to use this with Webpack 2. Nothing more, nothing less. |
why do you think it's broken? most of people still use it for their projects |
@graingert actually webpack 2 is potentially much more broken, because it reifies more strongly incorrect ES module semantics that will definitely break when module loading in node is resolved, which is why Airbnb will likely not use webpack 2, and why I strongly recommend everybody avoid using non-babel |
@ljharb can you please elaborate, or link to relevant discussion? |
@xzyfer I'm specifically referring to when you |
Since this was linked on reddit and before everyone throws @ljharb under the bus, first read this cogent comment explaining the situation. Jordan's just the messenger here. The actual spec is where this is all going down and where you should raise your pitchforks 😄 |
Nevermind, it's right on Reddit, they opened a discussion about this (although as from the date of this comment it only has 2 comments). |
@ysangkok can you rebase this PR? |
@graingert ok now? |
No description provided.