You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to include sourcemaps for a dependency that has been linked. npm link mydep
This is working with the caveat that the sourcemaps appear under the same root src/ in chrome devtools. This is a problem b/c the linked node_module sourcemaps appear mixed with my applications sourcemaps and will be overwritten by my app if any conflicts exist.
🐛 bug report
I am trying to include sourcemaps for a dependency that has been linked.
npm link mydep
This is working with the caveat that the sourcemaps appear under the same root
src/
in chrome devtools. This is a problem b/c the linked node_module sourcemaps appear mixed with my applications sourcemaps and will be overwritten by my app if any conflicts exist.possibly related to #1801?
🎛 Configuration (.babelrc, package.json, cli command)
🤔 Expected Behavior
I would expect any sourcemaps found for node_modules would be served at a different root. See next section for an example
😯 Current Behavior
currently they are served from the same
/src
root.ex.
app
mydep
The source maps in chrome devtools will appear as:
I would expect them to appear as:
The source maps in chrome devtools will appear as:
💁 Possible Solution
🔦 Context
Being able to correctly view sourcemaps for linked dependencies is useful when attempting to debug a package.
💻 Code Sample
just link any node_module w/ built source maps to your app
🌍 Your Environment
The text was updated successfully, but these errors were encountered: