ember-tooling / ember-language-server Goto Github PK

Hey,

I am working on quite a large codebase and language server burns my CPU on 100% for long periods, seeming to never finish (left it running for 30minutes).

How can I debug what's actually happening?

Version 3.4.0 of mocha just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

• update name to @ember-tooling/ember-language-server
  

  ember-language-server/package.json

  Line 2 in 2583961

  "name": "@lifeart/ember-language-server",

• Update repo url
  

  ember-language-server/package.json

  Line 16 in 2583961

  "url": "https://github.com/lifeart/ember-language-server.git"

As of today, atom supports language servers too! Great news for the adoption of this project. What are next steps for making at atom plug-in?

http://blog.atom.io/2017/09/12/announcing-atom-ide.html

If there is a custom .eslintrc.js file in the component folders, the language server thinks there is a component called .eslintrc and provides autocompletion.

We should use https://www.appveyor.com/ to test this project on Windows too given the amount of filesystem stuff we do

• Add NPM_TOKEN for ember-tooling org
• Update package.json #394
• Make workflow manually runnable

Version 7.0.29 of @types/node just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

• autocompletion for named arguments of built in helpers like action
• autocompletion for own helpers (probably needs some discussion as what to provide, maybe we can use JSDoc information?)

• autocompletion for properties of built in components like link-to, input or textarea
• autocompletion for own components (probably needs some discussion as what to provide, maybe if a property is marked as public in JSDoc?)

Currently addon projects are not supported. Most of the features aren't working at all, or they are not really useful (e.g. the definition provider for templates provides the app re-export).

The demo language server is designed to move the compiled output into the vscode extension.
Since we want to keep the language server decoupled from the editor/IDE plugins the compiled output should stay in the current folder.

I'm using @lifeart's fork of this, and found that trying to use go-to definition on 'this.foo' doesn't work as expected.

This is using https://github.com/NullVoxPopuli/coc-ember

https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

It would be nice if this was configurable:
https://github.com/emberwatch/ember-language-server/blob/master/src/server.ts#L82-L90

My cpu usage spikes up to 100% on one of my cores when this plugin is enabled and I think it's due to big directories not in the stock exclude path.

Use the node.js/TypeScript example server code.

cc @t-sauer

Components that only have a template and no JS file are currently not indexed.

• in relationships of the model itself
• in store methods (e.g. find, findAll, query,...)

While module unification is coming, at the moment many users are still using pods for larger projects.

Using vscode, it seems "go to definition" only works for relative paths in .js files when executing it with the cursor over an import path string. It also seems there is no support yet for namespaced components which use the "::" syntax. Is there any plan to support namespaced/absolute paths in these scenarios? I would be very interested in helping add this support though i might need some guidance getting up to speed on how to run and debug the server from vscode. thanks!

Version 3.0.5 of ts-node just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As ts-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

This is because it looks for the presence of ember-cli-build.js, which is not present in V2 Addons. I'd like ELS so I at least get template linting support in VSCode.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Version 2.4.1 of typescript just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hi,
I was trying to get this working with sublime, as I seem to be one of the few who have not switched to vscode.
There is this LSP-package which allows a generic way to add language clients:
https://lsp.readthedocs.io/en/latest/#client-config

I can't find the command to start the language server. I guess it's because Ember-cli starts it. I hope you could help me out there or even say if it can be done with sublime text without too much work.

Cheers and keep up the good work.

A code lens that displays which addon a certain component/helper/modifier invocation comes from.

This came from @locks, moving this to here for tracking.

Enable features like "Go To Definition" for injected services.

• Add workflow_dispatch: so we can run manually
• Update branches it activates for to master
  

  ember-language-server/.github/workflows/ci.yml

  Line 6 in 3b9d0f5

  - component-context-info-origin

• Update to use standard secrets.GITHUB_TOKEN
  

  ember-language-server/.github/workflows/ci.yml

  Line 131 in 3b9d0f5

  GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}

As more and more of the community embraces TypeScript, it'll increasingly be the case that at least a reasonably large subset of users will have TypeScript definitions for their components, etc. Resolving those for completion would be a big win.

Builds running with npm2 are currently failing because we import the package estree (which is actually @types/estree) which is only installed as a dependency of @types/esprima.
Somehow require doesn't seem to resolve a scoped module if it is nested inside another module but I haven't verified that yet.
Since npm3 tries to keep the dependency tree flat @types/estree is located directly in node_modules and we don't have the problem there. npm2 on the other side puts the dependency into the node_modules of @types/esprima which somehow makes it unusable.

My suggestion would be to include @types/estree in our package.json since we directly use it so we shouldn't rely on esprima to provide it for us.

Version 5.4.3 of tslint just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 8.0.49 of @types/node was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 3.13.0 of vscode-languageserver-protocol was just published.

This version is covered by your current version range and after updating it in your project the build failed.

vscode-languageserver-protocol is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi! Thanks for creating this awesome language server for ember.

I'm having trouble setting it up to work with vim using the LanguageClient-neovim plugin. The easiest way to set up language servers with this plugin is to specify how to run the language server over stdin. Ex: javascript': ['/Users/samueljclopton/javascript-typescript-langserver/bin/language-server-stdio'] and 'ruby': ['solargraph stdio']. Not quire sure what args start-server.js is expecting, so any help here would be appreciated.

If the Glimmer parser encounters a problem we should be able to provide these errors as diagnostics (pretty much like a linter error).