Prevent the Babel plugin from breaking the output of babel-node #374
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #359.
The tagger code inserted by the babel plugin at the end of every file is an IIFE, which happens to break
babel-node
output when it's loaded. This happens because the code is added to every line that is evaluated by the REPL, so the lines now end with(function() { return; })()
, which makes the REPL outputundefined
for every line.By changing the IIFE from being wrapped in parens to a variable declaration, the output is no longer
undefined
for every line.The tests pass and from manual testing it doesn't break anything. @nfcampos want to take a look?
Thanks to @loganfsmyth for the help on the Babel slack!