4 ms·
So it looks like they still won't be supporting ES6 module imports, which just screws everything up when trying to do anything with js. Sad to see.
by dvcc 11y ago
So it looks like they still won't be supporting ES6 module imports, which just screws everything up when trying to do anything with js. Sad to see.
- AaronFriel 11y agoIt looks like they're working on it and it's supported in the latest Node Tools releases? https://github.com/Microsoft/nodejstools/issues/77#issuecomment-174141628 https://github.com/Microsoft/nodejstools/issues/77#issuecomm...
- dsp1234 11y agoSpecifically: "This feature is currently available if you switch on the new ES6 IntelliSense Preview mode, available in the latest NTVS release. "
- dvcc 11y agoI think that is just for the NTVS plugin but VS itself still does not: https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/7017377-support-for-es6-modules https://visualstudio.uservoice.com/forums/121579-visual-stud...
- WorldMaker 11y agoThe release notes point to a switch to "Salsa" for JS intellisense. Salsa is based on the TS intellisense service (it is run by the TS intellisense service) and the same one used these days by VS Code. At least what I've seen in VS Code, Salsa seems fine with ES2015 import syntax and intellisense. (That said, almost all of my code is TS, so I'm not sure I've hit any specific use cases you are particularly looking for support in.)
- dvcc 11y agoDid the update today and gave it a try but it looks like it still complains on the imports, but JSX parsing did still improve at least!