Activity

1. Fishrock123 commented on Jun 2, 2017

   

   Fishrock123

   on Jun 2, 2017

   Contributor

   More actions

   Hmm, strange, it works for me in the repl:

   > let foo = 'bar';
   undefined
   > throw `${foo}baz`;
   barbaz
   

   👍React with 👍2Reacted by Tobias Nießen and Vse Mozhe Buty
2. mscdex

   added

   v8.x

   v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.

   on Jun 2, 2017
3. cjihrig commented on Jun 2, 2017

   

   cjihrig

   on Jun 2, 2017

   Contributor

   More actions

   I can't reproduce on macOS with 8.0.0 or master.

   $ node test.js 
   
   /Users/cjihrig/iojs/node/test.js:2
   throw `${foo}baz`;
   ^
   barbaz
   
4. vsemozhetbyt commented on Jun 2, 2017

   

   vsemozhetbyt

   on Jun 2, 2017

   Contributor

   More actions

   @Ryuno-Ki Can you provide the full literal output with the thrown error?
5. jasnell commented on Jun 2, 2017

   

   jasnell

   on Jun 2, 2017

   Member

   More actions

   Also unable to reproduce.
6. bnoordhuis commented on Jun 3, 2017

   

   bnoordhuis

   on Jun 3, 2017

   Member

   More actions

   @Ryuno-Ki Are you using source code processors / transpilers like babel?
7. Ryuno-Ki commented on Jun 6, 2017

   

   Ryuno-Ki

   on Jun 6, 2017

   Author

   More actions

   Ah, maybe it is not a bug, but a feature …

   $ cat test.js
   let foo = "bar"
   throw `${foo}baz`
   $ node test.js 
   $HOME/Projects/$REPO/test.js:2
   throw `${foo}baz`
   ^
   barbaz

   But after adding an npm script for it and running that, I get

   $ npm run throwaway
   > $REPO@$VERSION throwaway $HOME/Projects/$REPO
   > node ./test.js
   
   
   $HOME/Projects/$REPO/test.js:2
   throw `${foo}baz`
   ^
   barbaz
   npm ERR! code ELIFECYCLE
   npm ERR! errno 1
   npm ERR! $REPO@$VERSION throwaway: `node ./test.js`
   npm ERR! Exit status 1
   npm ERR! 
   npm ERR! Failed at the $REPO@$VERSION throwaway script.
   npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
   
   npm ERR! A complete log of this run can be found in:
   npm ERR!     $HOME/.npm/_logs/2017-06-06T09_39_00_354Z-debug.log

   So it could be, that it outputted me a raw view of the file's content … In that case, sorry for the noise :)
8. bnoordhuis

   closed this as completedon Jun 6, 2017
9. bnoordhuis

   added

   invalidIssues and PRs that are invalid.Issues and PRs that are invalid.

   on Jun 6, 2017
10. refack commented on Jun 6, 2017

    

    refack

    on Jun 6, 2017

    Contributor

    More actions

    @Ryuno-Ki thank you for the clarification and follow up.