Skip to content
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

Document howto replace webpack #135

Open
alexanderadam opened this issue Jan 24, 2019 · 3 comments
Open

Document howto replace webpack #135

alexanderadam opened this issue Jan 24, 2019 · 3 comments

Comments

@alexanderadam
Copy link

It would be nice if it would be documented how webpack can be replaced by something else in an application.

@kvirani
Copy link

kvirani commented Apr 2, 2019

Great idea @alexanderadam. Which replacement did you have in mind for your instance (Parcel?). Were you able to successfully replace Webpack with it? How did that go? Would love any details you could provide.

@westonganger
Copy link
Contributor

Laravel Mix is what I switched to. I agree this should be documented, as well as the asset system in general.

@alexanderadam
Copy link
Author

alexanderadam commented Apr 4, 2019

@kvirani I didn't replace anything yet. I wouldn't want the documentation to be focused on a particular replacement. JavaScript tooling is constantly changing and the documentation shouldn't focus on a something that might be obsolete next month. Maybe parcel is 'hip' right now or maybe rollup or pundle. Or maybe someone wants to migrate a project from gulp or browserify.

@westonganger would you share how you did it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants