You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The extension is loaded on startup for every project. This is due to the activationEvents set to * in the package.json. Extensions with this activation event effectively delay VS Code from becoming active.
To ensure a great end user experience, please use this activation event in your extension only when no other activation events combination works in your use-case.
Since, there are other activation event combination open, I would consider this a bug. As a comparsion, ESLint uses onStartUpFinished.
What code is needed to reproduce this issue?
Open any project. You can see stylelint is loaded by running the command Developer: Show Running Extensions.
What vscode-stylelint configuration is needed to reproduce the bug?
No config required.
Is this issue related to autofix? (editor.codeActionsOnSave)
No
Which version of vscode-stylelint are you using?
0.86.0
Which version of stylelint are you using?
Latest version.
Does your issue relate to non-standard syntax (e.g. SCSS, nesting, etc.)?
It is a global issue, it is not tied to a specific syntax.
What did you expect to happen?
I would expect stylelint to be loaded only when a file with CSS-like syntax is open.
What actually happened (e.g. what warnings or errors you are getting)?
The extension is always loaded.
While I realise that stylelint targets many different file types and it is hard to target all of these with onLanguage activation events. Maybe, this would be adequate:
* refactor: Activate on `onStartupFinished`
Closes#214
Stops this extension from slowing VS Code during startup.
* feat: add API, formatter registration notification
Added so that formatter test can wait until formatter is registered
since VS Code has no API to check if a formatter with a given ID exists.
See microsoft/vscode#135674
* docs: add entry to changelog
The extension is loaded on startup for every project. This is due to the
activationEvents
set to*
in thepackage.json
. Extensions with this activation event effectively delay VS Code from becoming active.The VS Code docs gives the following advice on
*
:Since, there are other activation event combination open, I would consider this a bug. As a comparsion, ESLint uses
onStartUpFinished
.Open any project. You can see stylelint is loaded by running the command
Developer: Show Running Extensions
.No config required.
No
0.86.0
Latest version.
It is a global issue, it is not tied to a specific syntax.
I would expect stylelint to be loaded only when a file with CSS-like syntax is open.
The extension is always loaded.
While I realise that stylelint targets many different file types and it is hard to target all of these with
onLanguage
activation events. Maybe, this would be adequate:I suggest at the very least, you can change the activation event to
onStartUpFinished
to ensure it does not delay startup of VS Code.The text was updated successfully, but these errors were encountered: