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
{{ message }}
This repository has been archived by the owner on May 11, 2018. It is now read-only.
I have a Node web app where both the server and frontend use Babel. The frontend is served using webpack-dev-middleware in development, so I can just launch the app in one command with babel-node.
{
"presets": [
["env", {
"debug": true,
"modules": false
// no "targets" for now, just defaulting to "latest" preset
}],
"react"
],
"env": {
"development": {
"plugins": ["react-hot-loader/babel"]
}
}
}
When the debug option is set to true in both files, only the output for the server (Node) one is shown - I would expect both to be shown. If I remove that option from the Node .babelrc, the frontend debug output then shows up fine with all the stuff from babel-preset-latest as I expect.
It's important to note that the bug doesn't affect actual functionality and the setup works great otherwise.
This issue has been automatically marked as stale because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions 👌!
I have a Node web app where both the server and frontend use Babel. The frontend is served using
webpack-dev-middleware
in development, so I can just launch the app in one command withbabel-node
.Root level
.babelrc
for server:Subdirectory
.babelrc
for frontend:When the
debug
option is set totrue
in both files, only the output for the server (Node) one is shown - I would expect both to be shown. If I remove that option from the Node.babelrc
, the frontend debug output then shows up fine with all the stuff frombabel-preset-latest
as I expect.It's important to note that the bug doesn't affect actual functionality and the setup works great otherwise.
Edit: I expect it has something to do with the
hasBeenLogged
flag variable.The text was updated successfully, but these errors were encountered: