-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No source maps #106
Comments
Hmm.. Have you tried to use inlined source maps? I've got them working in my projects. |
Closing this one since there is not activity lately. |
hi @milankinen - this is still an issue, please reopen. I'm currently using watchify v3.7.0 & livereactload 2.2.4 - when running watchify without In my case I am using babelify transform but specifying it via the "browserify": {
"transform": [
"babelify",
"brfs"
]
}, P.S. I have tried with livereactload 2.2.1 through 2.2.3 - just in case it was a regression in the last couple of versions ... they all exhibit the same behaviour of stripping the sourcemap from the browserified bundle. |
Thanks! Re-opened the issue. Could you test the new (beta) version |
hi there, just gave it a shot ... still no source map in the output, I'm piping through
my full command line looks like so: ./node_modules/.bin/watchify \
-v --debug --delay=100 --fast --dg=0 \
-t babelify -p livereactload \
/my/project/client-entry-point.js \
-o './node_modules/.bin/exorcist /my/project/dist/bundle.js.map > /my/project/dist/bundle.js'
I have a {
"presets" : [
"es2015",
"react"
],
"compact" : true,
"minified" : false,
"comments" : true,
"sourceMaps" : true,
"env" : {
"development" : {
"plugins" : [
[ "react-transform", { "transforms": [ { "transform": "livereactload/babel-transform", "imports": ["react"] } ] } ]
]
}
}
} |
Should be fixed now in |
Seems that the plugin doesn't support source maps.
Running it like this doesn't include any source maps into my build:
However, compiling my bundle without the plugin gets me all the source maps inlined:
Is there a way to add that feature?
The text was updated successfully, but these errors were encountered: