Closed RamonGebben closed 8 years ago
If you want to create a webpack
loader: go for it. It should work right now with https://github.com/hughsk/ify-loader though
Also welcome to PR to this repo if you like: I reckon it should be simple enough. I'm an opponent of webpack in general, but I dislike most of ES6 more so... yeah, PR definitely welcome!
Sure. Putting together the loader would not be that much effort, I will spend some time on it over the weekend. The only thing I'm not sure about is how to facilitate both webpack and browserify from the same package.
Do you have any ideas on how to approach this problem or is the only option to make another package called es2020-loader?
webpack loader could sit at es2020/webpack
or es2020/loader
perhaps? :sparkles:
You mean create an "Organization" account and put the repo there?
Then the most logical name for the package would be es2020-loader
since the convention is to name loaders like something-loader
.
Oh no - I dislike tiny orgs like that. If you're not going to PR it to this repo, I'd suggest creating it under your name and then we'll just link to it from here 😁
Yeahhh, so I really can't be bothered writing this - if anyone wants to write a webpack
loader, go for it! Happy to link to it from the docs :sparkles: Closing for now then
Currently you need a build process with relies on Browserify. Would it be an idea to also include a webpack loader so that the end user can make a choice on what to use.
This might also increase the usage since a lot a companies are building on top of webpack and that way you could tome down the es6 magic in existing (webpack based) projects.