Mixing
Heroku - Build fail “LoadError: canot load such file — coffee_script”
As the title states, I'm unable to complete a build on Heroku after removing gem 'coffee-rails' from my Gemfile.
Below is the error message as well as a few lines before that show that it is removing coffee-script.
remote: Removing coffee-script (2.4.1)
remote: Removing coffee-script-source (1.12.2)
remote: Removing coffee-rails (4.2.2)
remote: The latest bundler is 2.0.0.pre.3, but you are currently running 1.15.2.
remote: To update, run `gem install bundler --pre`
remote: -----> Installing node-v8.10.0-linux-x64
remote: -----> Detecting rake tasks
remote: -----> Preparing app for Rails asset pipeline
remote: Running: rake assets:precompile
remote: Yarn executable was not detected in the system.
remote: Download Yarn at https://yarnpkg.com/en/docs/install
remote: rake aborted!
remote: LoadError: cannot load such file -- coffee_script
remote: /tmp/build_dc46e31874491817c9a77e17cf3ac4d1/vendor/bundle/ruby/2.4.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
To me, it looks like this could be an issue with Bootsnap on Heroku.
Steps I've taken:
- Removed
gem 'coffee-rails'Ranbundle update. - Removed all references to coffee script per this answer
- Added, committed and pushed the updated Gemfile and Gemfile.lock to my master branch.
- Ran
rake tmp:cache:clearon Heroku via bash. - Restarted dyno
At this point, I'm tempted to just keep the gem installed as I've confirmed that the build passes.
Any assistance would be wonderful.
Edit: I have staging app setup that had this same issue. Simply starting a new staging app/remote solved the issue, so that's why I'm leaning towards a cache issue.
ruby-on-rails heroku assets
asked Jan 2 at 20:35
troxwalttroxwalt
141210
add a comment |
As the title states, I'm unable to complete a build on Heroku after removing gem 'coffee-rails' from my Gemfile.
Below is the error message as well as a few lines before that show that it is removing coffee-script.
remote: Removing coffee-script (2.4.1)
remote: Removing coffee-script-source (1.12.2)
remote: Removing coffee-rails (4.2.2)
remote: The latest bundler is 2.0.0.pre.3, but you are currently running 1.15.2.
remote: To update, run `gem install bundler --pre`
remote: -----> Installing node-v8.10.0-linux-x64
remote: -----> Detecting rake tasks
remote: -----> Preparing app for Rails asset pipeline
remote: Running: rake assets:precompile
remote: Yarn executable was not detected in the system.
remote: Download Yarn at https://yarnpkg.com/en/docs/install
remote: rake aborted!
remote: LoadError: cannot load such file -- coffee_script
remote: /tmp/build_dc46e31874491817c9a77e17cf3ac4d1/vendor/bundle/ruby/2.4.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
To me, it looks like this could be an issue with Bootsnap on Heroku.
Steps I've taken:
- Removed
gem 'coffee-rails'Ranbundle update. - Removed all references to coffee script per this answer
- Added, committed and pushed the updated Gemfile and Gemfile.lock to my master branch.
- Ran
rake tmp:cache:clearon Heroku via bash. - Restarted dyno
At this point, I'm tempted to just keep the gem installed as I've confirmed that the build passes.
Any assistance would be wonderful.
Edit: I have staging app setup that had this same issue. Simply starting a new staging app/remote solved the issue, so that's why I'm leaning towards a cache issue.
ruby-on-rails heroku assets
asked Jan 2 at 20:35
troxwalttroxwalt
141210
Try deletingtmp/cache/bootsnap-compile-cacheandtmp/cache/bootsnap-load-path-cache
– Tom
Jan 2 at 21:16
@Tom Thank you - I did remove those, but they are recreated on dyno restart.
– troxwalt
Jan 2 at 21:34
add a comment |
As the title states, I'm unable to complete a build on Heroku after removing gem 'coffee-rails' from my Gemfile.
Below is the error message as well as a few lines before that show that it is removing coffee-script.
remote: Removing coffee-script (2.4.1)
remote: Removing coffee-script-source (1.12.2)
remote: Removing coffee-rails (4.2.2)
remote: The latest bundler is 2.0.0.pre.3, but you are currently running 1.15.2.
remote: To update, run `gem install bundler --pre`
remote: -----> Installing node-v8.10.0-linux-x64
remote: -----> Detecting rake tasks
remote: -----> Preparing app for Rails asset pipeline
remote: Running: rake assets:precompile
remote: Yarn executable was not detected in the system.
remote: Download Yarn at https://yarnpkg.com/en/docs/install
remote: rake aborted!
remote: LoadError: cannot load such file -- coffee_script
remote: /tmp/build_dc46e31874491817c9a77e17cf3ac4d1/vendor/bundle/ruby/2.4.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
To me, it looks like this could be an issue with Bootsnap on Heroku.
Steps I've taken:
- Removed
gem 'coffee-rails'Ranbundle update. - Removed all references to coffee script per this answer
- Added, committed and pushed the updated Gemfile and Gemfile.lock to my master branch.
- Ran
rake tmp:cache:clearon Heroku via bash. - Restarted dyno
At this point, I'm tempted to just keep the gem installed as I've confirmed that the build passes.
Any assistance would be wonderful.
Edit: I have staging app setup that had this same issue. Simply starting a new staging app/remote solved the issue, so that's why I'm leaning towards a cache issue.
ruby-on-rails heroku assets
asked Jan 2 at 20:35
troxwalttroxwalt
141210
As the title states, I'm unable to complete a build on Heroku after removing gem 'coffee-rails' from my Gemfile.
Below is the error message as well as a few lines before that show that it is removing coffee-script.
remote: Removing coffee-script (2.4.1)
remote: Removing coffee-script-source (1.12.2)
remote: Removing coffee-rails (4.2.2)
remote: The latest bundler is 2.0.0.pre.3, but you are currently running 1.15.2.
remote: To update, run `gem install bundler --pre`
remote: -----> Installing node-v8.10.0-linux-x64
remote: -----> Detecting rake tasks
remote: -----> Preparing app for Rails asset pipeline
remote: Running: rake assets:precompile
remote: Yarn executable was not detected in the system.
remote: Download Yarn at https://yarnpkg.com/en/docs/install
remote: rake aborted!
remote: LoadError: cannot load such file -- coffee_script
remote: /tmp/build_dc46e31874491817c9a77e17cf3ac4d1/vendor/bundle/ruby/2.4.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
To me, it looks like this could be an issue with Bootsnap on Heroku.
Steps I've taken:
- Removed
gem 'coffee-rails'Ranbundle update. - Removed all references to coffee script per this answer
- Added, committed and pushed the updated Gemfile and Gemfile.lock to my master branch.
- Ran
rake tmp:cache:clearon Heroku via bash. - Restarted dyno
At this point, I'm tempted to just keep the gem installed as I've confirmed that the build passes.
Any assistance would be wonderful.
Edit: I have staging app setup that had this same issue. Simply starting a new staging app/remote solved the issue, so that's why I'm leaning towards a cache issue.
ruby-on-rails heroku assets
ruby-on-rails heroku assets
asked Jan 2 at 20:35
troxwalttroxwalt
141210
asked Jan 2 at 20:35
troxwalttroxwalt
141210
asked Jan 2 at 20:35
troxwalttroxwalt
141210
asked Jan 2 at 20:35
troxwalttroxwalt
141210
asked Jan 2 at 20:35
troxwalttroxwalt
141210
141210
Try deletingtmp/cache/bootsnap-compile-cacheandtmp/cache/bootsnap-load-path-cache
– Tom
Jan 2 at 21:16
@Tom Thank you - I did remove those, but they are recreated on dyno restart.
– troxwalt
Jan 2 at 21:34
add a comment |
Try deletingtmp/cache/bootsnap-compile-cacheandtmp/cache/bootsnap-load-path-cache
– Tom
Jan 2 at 21:16
@Tom Thank you - I did remove those, but they are recreated on dyno restart.
– troxwalt
Jan 2 at 21:34
Try deleting
tmp/cache/bootsnap-compile-cache and tmp/cache/bootsnap-load-path-cache– Tom
Jan 2 at 21:16
Try deleting
tmp/cache/bootsnap-compile-cache and tmp/cache/bootsnap-load-path-cache– Tom
Jan 2 at 21:16
@Tom Thank you - I did remove those, but they are recreated on dyno restart.
– troxwalt
Jan 2 at 21:34
@Tom Thank you - I did remove those, but they are recreated on dyno restart.
– troxwalt
Jan 2 at 21:34
add a comment |
0
active
oldest
votes
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',
autoActivateHeartbeat: false,
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%2f54012826%2fheroku-build-fail-loaderror-canot-load-such-file-coffee-script%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f54012826%2fheroku-build-fail-loaderror-canot-load-such-file-coffee-script%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
Try deleting
tmp/cache/bootsnap-compile-cacheandtmp/cache/bootsnap-load-path-cache– Tom
Jan 2 at 21:16
@Tom Thank you - I did remove those, but they are recreated on dyno restart.
– troxwalt
Jan 2 at 21:34