Webpacker: enable watch mode or unhook webpacker:compile from assets:precompile task in Rails?
up vote
0
down vote
favorite
Rails server running Webpacker compiler under the hood compiles all the files and not just modified files on reload.
I tried enabling the watch mode in webpacker.yml under dev_server but did not help. So either of these two things I want to do in order to resolve this issue:
How to enable the watch mode in Webpacker so that everytime an asset is modified, the only touched asset will be recompiled and hence will fix the reloading to make development a breeze.
Since I'm unable to find any solution to the 1st Point, I want to unhook the Webpacker:compile task from assets:precompile. Although I could unhook it on production by disabling the
WEBPACKER_PRECOMPILEenvironment variable tofalseand then compiling those assets manually using./bin/webpack. However, I'm unable to achieve the result locally when I run
export WEBPACKER_PRECOMPILE=false && rails s
To try out the 1st Point, I ran rails s in one tab and ./bin/webpack -w in another. To my surprise, the watch mode with the latter command only compiles the touched file reducing the compilation time to under 1s. However, after reloading the page rails s again compiles all the assets which take almost a minute to finish.
ruby-on-rails webpacker
asked Nov 20 at 12:37
codef0rmer
8,08583872
add a comment |
up vote
0
down vote
favorite
Rails server running Webpacker compiler under the hood compiles all the files and not just modified files on reload.
I tried enabling the watch mode in webpacker.yml under dev_server but did not help. So either of these two things I want to do in order to resolve this issue:
How to enable the watch mode in Webpacker so that everytime an asset is modified, the only touched asset will be recompiled and hence will fix the reloading to make development a breeze.
Since I'm unable to find any solution to the 1st Point, I want to unhook the Webpacker:compile task from assets:precompile. Although I could unhook it on production by disabling the
WEBPACKER_PRECOMPILEenvironment variable tofalseand then compiling those assets manually using./bin/webpack. However, I'm unable to achieve the result locally when I run
export WEBPACKER_PRECOMPILE=false && rails s
To try out the 1st Point, I ran rails s in one tab and ./bin/webpack -w in another. To my surprise, the watch mode with the latter command only compiles the touched file reducing the compilation time to under 1s. However, after reloading the page rails s again compiles all the assets which take almost a minute to finish.
ruby-on-rails webpacker
asked Nov 20 at 12:37
codef0rmer
8,08583872
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Rails server running Webpacker compiler under the hood compiles all the files and not just modified files on reload.
I tried enabling the watch mode in webpacker.yml under dev_server but did not help. So either of these two things I want to do in order to resolve this issue:
How to enable the watch mode in Webpacker so that everytime an asset is modified, the only touched asset will be recompiled and hence will fix the reloading to make development a breeze.
Since I'm unable to find any solution to the 1st Point, I want to unhook the Webpacker:compile task from assets:precompile. Although I could unhook it on production by disabling the
WEBPACKER_PRECOMPILEenvironment variable tofalseand then compiling those assets manually using./bin/webpack. However, I'm unable to achieve the result locally when I run
export WEBPACKER_PRECOMPILE=false && rails s
To try out the 1st Point, I ran rails s in one tab and ./bin/webpack -w in another. To my surprise, the watch mode with the latter command only compiles the touched file reducing the compilation time to under 1s. However, after reloading the page rails s again compiles all the assets which take almost a minute to finish.
ruby-on-rails webpacker
asked Nov 20 at 12:37
codef0rmer
8,08583872
Rails server running Webpacker compiler under the hood compiles all the files and not just modified files on reload.
I tried enabling the watch mode in webpacker.yml under dev_server but did not help. So either of these two things I want to do in order to resolve this issue:
How to enable the watch mode in Webpacker so that everytime an asset is modified, the only touched asset will be recompiled and hence will fix the reloading to make development a breeze.
Since I'm unable to find any solution to the 1st Point, I want to unhook the Webpacker:compile task from assets:precompile. Although I could unhook it on production by disabling the
WEBPACKER_PRECOMPILEenvironment variable tofalseand then compiling those assets manually using./bin/webpack. However, I'm unable to achieve the result locally when I run
export WEBPACKER_PRECOMPILE=false && rails s
To try out the 1st Point, I ran rails s in one tab and ./bin/webpack -w in another. To my surprise, the watch mode with the latter command only compiles the touched file reducing the compilation time to under 1s. However, after reloading the page rails s again compiles all the assets which take almost a minute to finish.
ruby-on-rails webpacker
ruby-on-rails webpacker
asked Nov 20 at 12:37
codef0rmer
8,08583872
asked Nov 20 at 12:37
codef0rmer
8,08583872
asked Nov 20 at 12:37
codef0rmer
8,08583872
asked Nov 20 at 12:37
codef0rmer
8,08583872
asked Nov 20 at 12:37
codef0rmer
8,08583872
8,08583872
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
While looking at the Webpacker source, this idea struck me:
Use
./bin/webpack --watchcommand to run Webpack in the watch mode. This will recompile modified files only speeding up the feedback cycle.To unhook the Webpack compilation from the rails server, just set
compile: falseunderdevelopmentenvironment in webpacker.yml
answered Nov 21 at 7:17
codef0rmer
8,08583872
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53393163%2fwebpacker-enable-watch-mode-or-unhook-webpackercompile-from-assetsprecompile%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
While looking at the Webpacker source, this idea struck me:
Use
./bin/webpack --watchcommand to run Webpack in the watch mode. This will recompile modified files only speeding up the feedback cycle.To unhook the Webpack compilation from the rails server, just set
compile: falseunderdevelopmentenvironment in webpacker.yml
answered Nov 21 at 7:17
codef0rmer
8,08583872
add a comment |
up vote
0
down vote
While looking at the Webpacker source, this idea struck me:
Use
./bin/webpack --watchcommand to run Webpack in the watch mode. This will recompile modified files only speeding up the feedback cycle.To unhook the Webpack compilation from the rails server, just set
compile: falseunderdevelopmentenvironment in webpacker.yml
answered Nov 21 at 7:17
codef0rmer
8,08583872
add a comment |
up vote
0
down vote
up vote
0
down vote
While looking at the Webpacker source, this idea struck me:
Use
./bin/webpack --watchcommand to run Webpack in the watch mode. This will recompile modified files only speeding up the feedback cycle.To unhook the Webpack compilation from the rails server, just set
compile: falseunderdevelopmentenvironment in webpacker.yml
answered Nov 21 at 7:17
codef0rmer
8,08583872
While looking at the Webpacker source, this idea struck me:
Use
./bin/webpack --watchcommand to run Webpack in the watch mode. This will recompile modified files only speeding up the feedback cycle.To unhook the Webpack compilation from the rails server, just set
compile: falseunderdevelopmentenvironment in webpacker.yml
answered Nov 21 at 7:17
codef0rmer
8,08583872
answered Nov 21 at 7:17
codef0rmer
8,08583872
answered Nov 21 at 7:17
codef0rmer
8,08583872
answered Nov 21 at 7:17
codef0rmer
8,08583872
8,08583872
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53393163%2fwebpacker-enable-watch-mode-or-unhook-webpackercompile-from-assetsprecompile%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
