-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Test Salsa as the default JS infrastructure #3170
Comments
Tested that the browser opens as expected. |
@aeschli can you confirm that you did not crash with or without excluding |
@egamma I finally figured out how to exclude 'tmp' and 'node_modules' correctly (no leading '/' and restart). Completions now show. |
@aeschli thanks, can you include your jsconfig.json you used for ember, I'm working on the change notes. I will not forget to mention the restart. |
{
"exclude": [
"tmp", "node_modules"
],
"compilerOptions": {
"target": "ES6",
"module": "commonjs"
}
} |
Ember looks ok, i was able to get some IntelliSense with ember.d.ts, no crashes. |
I didn't try the Ember scenario, but given Martin and Chris tried it, I think its ok :) |
This is good news Salsa fixed the limitation we have with the 'default export'. @chrisdias you should mention this to MS teams that build ember apps 😄 |
Only the opening of the release notes in the browser needs to be tested across platforms
Salsa is now the default JS infrastructure.
storage://global/vscode.javascript-migration
).The text was updated successfully, but these errors were encountered: