Skip to content
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

Closed
3 tasks done
egamma opened this issue Feb 19, 2016 · 8 comments
Closed
3 tasks done

Test Salsa as the default JS infrastructure #3170

egamma opened this issue Feb 19, 2016 · 8 comments

Comments

@egamma
Copy link
Member

egamma commented Feb 19, 2016

Only the opening of the release notes in the browser needs to be tested across platforms

Salsa is now the default JS infrastructure.

  • you get an info message that Salsa is now the default when you open a .js file for the first time. The message provides you with the option to read the change notes/migration guide. Verify that this message is only shown once (the state is stored in (storage://global/vscode.javascript-migration).
  • follow migrating to Salsa guide to setup your JavaScript project to enable warnings etc.
  • use an Ember project setup to test Salsa. The old JavaScript service excluded several directories by default (e.g. tmp) which Salsa doesn't do. Verify the experience and in particular that Code doesn't crash.
npm install -g ember-cli
npm install -g bower
npm install -g ember-cli-windows

ember-cli-windows    (you may need to ‘Set-ExecutionPolicy Unrestricted -scope CurrentUser’ for this to execute)
npm install
bower install
ember serve

Then browse at localhost:4200 to run server.
@egamma egamma added this to the Feb 2016 milestone Feb 19, 2016
@egamma egamma changed the title Test Salsa as the default Test Salsa as the default JS infrastructure Feb 19, 2016
@egamma egamma mentioned this issue Feb 20, 2016
97 tasks
@aeschli
Copy link
Contributor

aeschli commented Feb 23, 2016

Tested that the browser opens as expected.
Wasn't able to get a good Ember experience. Completions, hovers never seem to complete. I excluded tmp and node_modules but not sure if that really worked due to lack of feedback and status.

@egamma
Copy link
Member Author

egamma commented Feb 23, 2016

Wasn't able to get a good Ember experience. Completions, hovers never seem to complete.

@aeschli can you confirm that you did not crash with or without excluding node_modules and tmp. I think we never had a good intellisense experience even when we tried to use the ember.d.ts.

@aeschli
Copy link
Contributor

aeschli commented Feb 23, 2016

@egamma I finally figured out how to exclude 'tmp' and 'node_modules' correctly (no leading '/' and restart). Completions now show.
Before all I got was 'Loading'. No visible crash, but also no useful behavior.

@egamma
Copy link
Member Author

egamma commented Feb 23, 2016

@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.

@aeschli
Copy link
Contributor

aeschli commented Feb 24, 2016

{
    "exclude": [
        "tmp", "node_modules" 
    ],

    "compilerOptions": {
        "target": "ES6",
        "module": "commonjs"
    }
}

@chrisdias
Copy link
Member

Ember looks ok, i was able to get some IntelliSense with ember.d.ts, no crashes.

@alexdima
Copy link
Member

I didn't try the Ember scenario, but given Martin and Chris tried it, I think its ok :)

@egamma
Copy link
Member Author

egamma commented Feb 25, 2016

Ember looks ok, i was able to get some IntelliSense with ember.d.ts, no crashes.

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 😄

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants