Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sourcemaps support is missing
See original GitHub issueI was trying to use sourcemaps for the SCSS files (as node-sass provide them) but it seems that feature has been omitted during development of this plugin.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:13 (7 by maintainers)
Top Results From Across the Web
source-map-support - npm
This module provides source map support for stack traces in node via the V8 stack trace API. It uses the source-map module to...
Read more >Angular 12 source map is missing in browser - Stack Overflow
We have upgraded to Angular 12 recently and facing a problem wherein the browser Source Map is missing and due to this we...
Read more >Troubleshooting Source Maps for JavaScript
Troubleshooting Source Maps · Verify a release is configured in your SDK · Verify artifacts are uploaded · Verify sourceMappingURL is present ·...
Read more >Sourcemaps not appearing in Browser UI
One of the source maps files you've uploaded, so we can review it and see if there may be something missing that's causing...
Read more >JavaScript source map upload - Bugsnag docs
See source map support for details. The source map upload API can be ... 400 - missing required param -indicates that the minifiedUrl...
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 Free
Top 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
Is this how the option is supposed to be passed?
When you say “split the output in code/map”, do you mean writing code to separate the embedded source map?
If so, I don’t think most, if not all, users would want to do that. The README says “Options are passed to node-sass”, so users would expect that all the options node-sass accepts would just work.
I’m not sure what the issue is that is preventing this function from working. Is it because of the
outFileparameter which states “enabling this option will not write the file on disk for you”?