feat: add support for indented syntax

.github/ISSUE_TEMPLATE/01-bug.yml

@@ -0,0 +1,46 @@
+name: "Bug report"
+description: Report an issue or possible bug
+labels: []
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for taking the time to file a bug report! Please fill out this form as completely as possible.
+
+        ✅ I am using the latest version of Some Sass.
+        ✅ I am using the latest version of my editor.
+  - type: input
+    id: editor
+    attributes:
+      label: In which editor is this a problem?
+      description: If you use an editor other than VS Code or VSCodium, please try to reproduce the issue in either of those editors and let us know if it works there or not.
+      value: Visual Studio Code
+    validations:
+      required: true
+  - type: textarea
+    id: bug-description
+    attributes:
+      label: Describe the bug
+    validations:
+      required: true
+  - type: textarea
+    id: bug-expectation
+    attributes:
+      label: What's the expected result?
+      description: Describe what you expect to happen.
+    validations:
+      required: true
+  - type: input
+    id: bug-reproduction
+    attributes:
+      label: Link to minimal reproducible example
+      description: 'A minimal reproduction is required. If a report is vague (e.g. just a generic error message) and has no reproduction, it may be closed. Not sure how to create a minimal example? [Read our guide](https://wkillerud.github.io/some-sass/contributing/reporting-bugs.html)'
+      placeholder: 'https://github.com/wkillerud/some-sass-issue-template'
+  - type: checkboxes
+    id: will-pr
+    attributes:
+      label: Participation
+      options:
+        - label:  I am willing to submit a pull request for this issue.
+          required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Ideas for new features, improvements
+    url: https://github.com/wkillerud/some-sass/discussions
+    about: Suggest additions or improvements to Some Sass in Discussions
+  - name: Questions when setting up Some Sass in an editor
+    url: https://github.com/wkillerud/some-sass/discussions
+    about: Please use Discussions if you have questions when configuring a language server client in a new editor

.gitignore

@@ -9,9 +9,7 @@ npm-debug.log*
 
 # Dependency directory
 node_modules/
-!vscode-extension/test/fixtures/node_modules
-!vscode-extension/test/fixtures/completion/node_modules
-!vscode-extension/test/fixtures/pkg-import/node_modules
+!vscode-extension/test/**/node_modules
 
 # Compiled and temporary files
 dist/
@@ -30,3 +28,6 @@ docs/book/
 
 .nx/cache
 .nx/workspace-data
+
+*.cpuprofile
+*.heapprofile

.nvmrc

@@ -1 +1 @@
-20.16.0
+20.17.0

.vscode/launch.json

@@ -22,17 +22,6 @@
 			],
 			"outFiles": ["${workspaceFolder}/vscode-extension/dist/browser-*.js"],
 			"autoAttachChildProcesses": true
-		},
-		{
-			"name": "Launch end-to-end tests",
-			"type": "extensionHost",
-			"request": "launch",
-			"runtimeExecutable": "${execPath}",
-			"args": [
-				"--extensionDevelopmentPath=${workspaceFolder}/vscode-extension",
-				"--extensionTestsPath=${workspaceFolder}/vscode-extension/test/e2e/suite",
-				"${workspaceFolder}/vscode-extension/test/fixtures/"
-			]
 		}
 	]
 }

README.md

@@ -1,13 +1,14 @@
 # Some Sass
 
-Some Sass is a [language server extension][langext] for [Visual Studio Code][vscode]. It brings improved code suggestions, documentation and code navigation for [SCSS][scss].
+Some Sass is a [language server extension][langext] for [Visual Studio Code][vscode]. It brings improved code suggestions, documentation and code navigation for both [SCSS][scss] and [indented] syntaxes.
 
 Some features include:
 
 - Full support for [`@use`][use] and [`@forward`][forward], including aliases, prefixes and hiding.
 - Workspace-wide code navigation and refactoring, such as Rename Symbol.
 - Rich documentation through [SassDoc][sassdoc].
 - Language features for [`%placeholders`][placeholder], both when using them and writing them.
+- Support for [both Sass syntaxes](https://sass-lang.com/documentation/syntax/).
 
 ![](./docs/src/images/highlight-reel.gif)
 

docs/src/README.md

@@ -1,13 +1,14 @@
 # Some Sass
 
-Some Sass is a [language server extension][langext] for [Visual Studio Code][vscode]. It brings improved code suggestions, documentation and code navigation for [SCSS][scss].
+Some Sass is a [language server extension][langext] for [Visual Studio Code][vscode]. It brings improved code suggestions, documentation and code navigation for both SCSS and indented Sass [syntaxes].
 
 Some features include:
 
 - Full support for [`@use`][use] and [`@forward`][forward], including aliases, prefixes and hiding.
 - Workspace-wide code navigation and refactoring, such as Rename Symbol.
 - Rich documentation through [SassDoc][sassdoc].
 - Language features for [`%placeholders`][placeholder], both when using them and writing them.
+- Support for both SCSS and intended [syntaxes].
 
 ![](./images/highlight-reel.gif)
 
@@ -35,7 +36,7 @@ To search click the magnifying class icon to the top left or press `s` on your k
 
 [lsp]: https://microsoft.github.io/language-server-protocol/
 [npm]: https://www.npmjs.com/package/some-sass-language-server
-[scss]: https://sass-lang.com/documentation/syntax/
+[syntaxes]: https://sass-lang.com/documentation/syntax/
 [use]: https://sass-lang.com/documentation/at-rules/use/
 [forward]: https://sass-lang.com/documentation/at-rules/forward/
 [langext]: https://code.visualstudio.com/api/language-extensions/language-server-extension-guide

docs/src/SUMMARY.md

@@ -23,6 +23,7 @@
 # Contributing to Some Sass
 
 - [New contributors](contributing/new-contributors.md)
+  - [Reporting bugs](contributing/reporting-bugs.md)
   - [Extensions for VS Code](contributing/extensions-for-vs-code.md)
   - [Language Server Protocol](contributing/language-server-protocol.md)
 - [Development environment](contributing/development-environment.md)
@@ -31,8 +32,8 @@
 - [Automated tests](contributing/automated-tests.md)
   - [Test coverage](contributing/test-coverage.md)
 - [Debugging](contributing/debugging.md)
-  - [Debugging in the browser](contributing/debugging-in-browser.md)
   - [Debugging unit tests](contributing/debugging-unit-tests.md)
-  - [Debugging end-to-end tests](contributing/debugging-e2e-tests.md)
+  - [Debugging performance](contributing/debugging-performance.md)
+  - [Debugging in the browser](contributing/debugging-in-browser.md)
 - [Releasing new versions](contributing/releases.md)
 - [Writing documentation](contributing/writing-documentation.md)

docs/src/contributing/architecture.md

@@ -1,6 +1,6 @@
 # Architecture
 
-Being a [language server extension](https://code.visualstudio.com/api/language-extensions/language-server-extension-guide), Some Sass consists of a [client](https://github.com/wkillerud/some-sass/blob/main/vscode-extension) and a [server](https://github.com/wkillerud/some-sass/blob/main/packages/language-server). The client starts the server when it opens a file with SCSS. This is called activation.
+Being a [language server extension](https://code.visualstudio.com/api/language-extensions/language-server-extension-guide), Some Sass consists of a [client](https://github.com/wkillerud/some-sass/blob/main/vscode-extension) and a [server](https://github.com/wkillerud/some-sass/blob/main/packages/language-server). The client starts the server when it opens a file with SCSS or Sass code. This is called activation.
 
 From there everything happens via [messages](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/).
 
@@ -18,17 +18,17 @@ The code for the server is divided in three packages:
 
 1. Language server
 2. Language services
-3. VS Code CSS language service – the SCSS parser and language features that are included in VS Code.
+3. VS Code CSS language service
 
 ### Language server
 
-This package handles communication with the language client, and not much else.
+This package handles communication with the language client, scans the workspace for files to parse them, and not much else.
 
 ### Language services
 
 This is where you find the functionality of the language server, organized in classes that inherit from a base `LanguageFeature` class.
 
-All features will parse the given document, but parses are cached for performance reasons. The flow looks something like this:
+All features will parse the given document, but parses are cached for performance. The flow looks something like this:
 
 ![](../images/architecture/parser-cache.png)
 
@@ -44,4 +44,6 @@ In addition to the parsed document, the cache also holds:
 
 ### VS Code CSS language service
 
-The project includes a private fork of the `vscode-css-languageservice` module. The original `vscode-css-languageservice` powers the CSS, SCSS and Less features in Visual Studio Code. Some Sass uses this module's parser and some of its language features. It's kept as a separate package to simplify updates, and to make it easier to send patches upstream.
+The project includes a private fork of the `vscode-css-languageservice` module. The original `vscode-css-languageservice` powers the CSS, SCSS and Less features in Visual Studio Code.
+
+Some Sass extends this module's parser and some of its language features to support both syntaxes. It's kept as a separate package to simplify updates, and to make it easier to send patches upstream.

docs/src/contributing/automated-tests.md

@@ -10,7 +10,7 @@ All packages in `packages/` have unit tests. To run them:
 npm run test
 ```
 
-The main test runner is [Vitest]. `vscode-css-languageservice` uses [Mocha].
+The test runner is [Vitest].
 
 Unit tests typically cover either a utility function or a language feature such as `doHover`. For language features the tests are typically split in several files, each focusing on part of the functionality of the language feature.
 
@@ -28,7 +28,7 @@ It also includes end-to-end tests for the web extension. To run them:
 npm run test:web
 ```
 
-The end-to-end tests have some overlap with the unit tests for language features, but are useful to confirm the communication between client and server works as expected.
+The end-to-end tests have some overlap with the unit tests for language features, but are useful to confirm the communication between client and server works as expected. It's also the most practical way to test the `language-server` module.
 
 ## Run all tests
 
@@ -39,4 +39,3 @@ npm run test:all
 ```
 
 [Vitest]: https://vitest.dev/
-[Mocha]: https://mochajs.org/

docs/src/contributing/building.md

@@ -26,6 +26,7 @@ If something unexpected happens with your build you can do a clean build:
 
 ```sh
 npm run clean
+npm run clean-install
 npm run build
 ```
 

docs/src/contributing/debugging-in-browser.md

@@ -12,7 +12,9 @@ npm run start:web
 
 This opens Visual Studio Code running as a [web extension host][exthost] in Chromium. The language server runs as a [web worker][worker], and is started when you open a Sass file.
 
-Open the Sass project you're using to test in the extension host window. If you don't have one you can open the folder `vscode-extension/test/fixtures/` in this repository.
+Open the Sass project you're using to test in the extension host window.
+If you don't have one you can find several `workspace/`
+directories inside `vscode-extension/test/e2e/` in this repository.
 
 ## Navigating the Chromium developer tools
 

docs/src/contributing/debugging-performance.md

@@ -0,0 +1,25 @@
+# Debugging performance
+
+Commonly refered to as performance profiling, this document explains how to run a performance test on Some Sass in Visual Studio Code.
+
+## Performance Profiling in Visual Studio Code
+
+To start a performance profile, first [launch the Some Sass extension](./debugging.md) from the Run and Debug pane in Visual Studio Code, then open a file with Sass code. Your debugging pane should look something like the image below.
+
+![](../images/debugging/debugging.png)
+
+The Call stack section lists Launch extension, which has four list items. The fourth list item, `node-server.js`, is the Some Sass language server. This is the program we want to profile.
+
+If you've ever done [performance profiling of JavaScript](https://code.visualstudio.com/docs/nodejs/profiling) in VS Code before, profiling Some Sass works the same way.
+
+Click or hover over the `node-server.js` row to show additional controls.
+
+![](../images/debugging/debugging-profiling-controls.png)
+
+Once the row is active you should see a list of icon buttons. The one we're interested in is the [circle with a dot in the center](https://code.visualstudio.com/docs/nodejs/profiling#_using-the-record-button), Take Performance Profile. Click it, and choose the [type of profile you want](https://code.visualstudio.com/docs/nodejs/profiling#_types-of-profiles). Unless you have specific plans, choose to stop the profile manually when asked.
+
+Do the operations you want to measure (hover, go to definition, edit some code, or what have you). Then, go back to the debugger and click the button again to stop the performance profiling.
+
+## Analyzing a performance profile
+
+You can open the recorded performance profile in Visual Studio Code and dig into the numbers. The VS Code documentation has some tips on [how to analyze a profile](https://code.visualstudio.com/docs/nodejs/profiling#_analyzing-a-profile).

docs/src/contributing/debugging-unit-tests.md

@@ -2,12 +2,14 @@
 
 This document assumes you use Visual Studio Code and have the [Vitest](https://marketplace.visualstudio.com/items?itemName=vitest.explorer) extension.
 
-Open a unit test file (excluding tests in `vscode-css-languageservice`, which use Mocha) and find the test you want to debug.
+Open a unit test file and find the test you want to debug.
 
 You should see an icon in the gutter. To debug the test, right click and select Debug test.
 
 ![](../images/debugging/debug-individual-test.gif)
 
+If you don't see any icons in the gutter it may be because the Vitest extension expects a different version of the `vitest` module. Try updating `vitest` in the repo and the Vitest extension, then restart VS Code.
+
 ## Test-driven development
 
 When you work on a language feature it's useful to set up a test and use that while developing.

docs/src/contributing/debugging.md

@@ -4,12 +4,14 @@ This page assumes you're using Visual Studio Code as the debugger. Go to the [Ru
 
 - Launch extension
 - Launch web extension
-- Launch integration tests
-- Launch web integration tests
 
 ## Launch extension
 
-This opens a new window of Visual Studio Code running as a [local extension host][exthost]. Open the Sass project you're using to test in the extension host window. If you don't have one you can open the folder `vscode-extension/test/fixtures/` in this repository.
+This opens a new window of Visual Studio Code running as a [local extension host][exthost].
+
+Open the Sass project you're using to test in the extension host window.
+If you don't have one you can find several `workspace/`
+directories inside `vscode-extension/test/e2e/` in this repository.
 
 ### Set breakpoints
 
@@ -30,7 +32,9 @@ You'll find the log output in two places:
 
 ## Launch web extension
 
-This opens a new window of Visual Studio Code running as a [web extension host][exthost]. Open the Sass project you're using to test in the extension host window. If you don't have one you can open the folder `vscode-extension/test/fixtures/` in this repository.
+This opens a new window of Visual Studio Code running as a [web extension host][exthost]. Open the Sass project you're using to test in the extension host window.
+If you don't have one you can find several `workspace/`
+directories inside `vscode-extension/test/e2e/` in this repository.
 
 Find `browser-server.js` in the `vscode-extension/dist/` folder to set breakpoints.