Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! I want to pursue a possibility that if we can have eject feature in webpacker.
I understand webpacker can configure all of webpack settings using
ConfigList
andConfigObject
. If a use case is just simple, then we can go with webpacker without having many custom settings, but if we want to customize, eventually we have to understand internal webpacker codes. In that case, I thinkwebpacker:eject
would be useful especially who knows webpack well and wants to configure directly.I believe
webpacker:eject
would be an escape route of a tall mountain. Even it might not be used, it will make people feel easy and it will strengthen webpacker. That being said, this PR is just POC and has a problem how to maintain the initialwebpack.config.js
. IMO,webpack.config.js
is not need to be completely compatible with webpacker's one, but just core logic is enough.eject will do following things:
webpack.config.js
while referring toconfig/webpacker.yml
's settings.config/webpack/loaders/*
will be used from generatedwebpack.config.js
. so for example, if you runbundle exec rake webpacker:install:elm
before, you can still useelm
.javascript_pack_tag
.yarn start
andyarn build
will be added.This PR works well with fresh
rails new
projects.I'm happy if I can get any feedbacks.
@gauravtiwari I saw this. do you have any idea regarding implementation?