Source map generation error when deploying to Heroku
See original GitHub issueI have been trying to add sass-brunch support to my app, which I deploy to Heroku. When I do so, I get a bunch of errors like the following:
error: Source map generation failed for 'tmp/build_bbbbbbbb/app/views/styles/foo.scss': ENOENT: no such file or directory, open '/tmp/build_bbbbbbbb/tmp/build_bbbbbbbb/app/views/styles/foo.scss'
I have tried both 3.0.0
and brunch/sass-brunch#master
, both of which work locally for me (but I am on Windows), and both of which fail on Heroku. I am using node 14.17.0
and npm 7.14.0
. Unsure if it matters, but my Heroku setup uses NODE_ENV=staging
.
Any ideas would be appreciated. Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Deploying app to Heroku with source-maps - Stack Overflow
Everything works perfect locally. I enabled source-maps in my webpack config and .map file is created. Problem is when I push app to...
Read more >Error: Cannot find module when deploying to heroku #198
Using latest next.js relase and a simple hello world index page with 0 dependencies fails to run on heroku with the following error: ......
Read more >Troubleshooting Node.js Deploys - Heroku Dev Center
Your Node.js deploy failed - now what? Start with these simple steps to troubleshoot a build issue. Check the buildpack.
Read more >Source Maps - Rollbar Docs
To successfully upload source maps, we will walk through the following steps. Raise descriptive JavaScript errors; Configure _rollbarConfig to support source ...
Read more >Node.js Error and Exception Tracking
If you run node with --source-map-support (and are generating source maps in your build), your stack traces should be automatically translated before they...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to make a workaround fix for myself for this by change this line: https://github.com/brunch/sass-brunch/blob/master/index.js#L124
To be:
This is now fixed on master