(chore) prettier --check (#768)

- add prettier --check
- Formatting everything

Note: If you use windows you might get a warning checking the first time. That's because git may do lf/crlf normalization. Just stage the files and they should magically disappear (because git recognizes that it's only lf/crlf differences)

Author: dummdidumm

.prettierignore

@@ -3,5 +3,8 @@ packages/svelte2tsx/test/*/samples/*/*sx
 packages/svelte2tsx/test/*/samples/*/*.svelte
 packages/svelte2tsx/test/sourcemaps/*.html
 packages/language-server/test/**/*.svelte
+packages/language-server/test/**/testfiles/**/*.ts
 packages/svelte-vscode/syntaxes/*.yaml
+**/dist
 .github/**
+.history/**

.vscode/settings.json

@@ -1,3 +1,3 @@
 {
-    "typescript.preferences.quoteStyle": "single",
+    "typescript.preferences.quoteStyle": "single"
 }

README.md

@@ -33,9 +33,7 @@ A `.svelte` file would look something like this:
     }
 </script>
 
-<button on:click="{handleClick}">
-    Count: {count}
-</button>
+<button on:click="{handleClick}">Count: {count}</button>
 
 <p>{count} * 2 = {doubled}</p>
 <p>{doubled} * 2 = {quadrupled}</p>
@@ -128,7 +126,7 @@ For tricker issues, you can run the tests with a debugger in VSCode by setting a
 
 Svelte is an MIT-licensed open source project with its ongoing development made possible entirely by the support of awesome volunteers. If you'd like to support their efforts, please consider:
 
-- [Becoming a backer on Open Collective](https://opencollective.com/svelte).
+-   [Becoming a backer on Open Collective](https://opencollective.com/svelte).
 
 Funds donated via Open Collective will be used for compensating expenses related to Svelte's development such as hosting costs. If sufficient donations are received, funds may also be used to support Svelte's development more directly.
 

docs/README.md

@@ -39,9 +39,7 @@ LSP-compatible editors, you can use an HTML comment with the `@component` tag:
 <!-- @component But only the last documentation comment will be used -->
 
 <main>
-    <h1>
-        Hello world
-    </h1>
+    <h1>Hello world</h1>
 </main>
 ```
 
@@ -66,7 +64,7 @@ The VS Code extension comes with its own syntax highlighting grammar which defin
 }
 ```
 
-To find out the scope of the things you want to highlight differently, you can use the scope inspector by entering the command "Developer: Inspect Editor Tokens and Scopes". The scope at the top of the section "textmate scopes" is what you are looking for. The current color is in the section "foreground" - you can use this to look up colors of other scopes if you want them to be the same color but don't know the color-code. 
+To find out the scope of the things you want to highlight differently, you can use the scope inspector by entering the command "Developer: Inspect Editor Tokens and Scopes". The scope at the top of the section "textmate scopes" is what you are looking for. The current color is in the section "foreground" - you can use this to look up colors of other scopes if you want them to be the same color but don't know the color-code.
 
 For more info on customizing your theme, [see the VS Code docs](https://code.visualstudio.com/docs/getstarted/themes#_customizing-a-color-theme).
 
@@ -95,8 +93,9 @@ If you have the `Babel Javascript` plugin installed, this may be the cause. Disa
 #### My Code does not get formatted
 
 Your default formatter for Svelte files may be wrong.
-- Mabye it's set to the old Svelte extension, if so, remove the setting
-- Maybe you set all files to be formatted by the prettier extension. Then you have two options: Either install `prettier-plugin-svelte` from npm, or tell VSCode to format the code with the `Svelte for VSCode extension`:
+
+-   Mabye it's set to the old Svelte extension, if so, remove the setting
+-   Maybe you set all files to be formatted by the prettier extension. Then you have two options: Either install `prettier-plugin-svelte` from npm, or tell VSCode to format the code with the `Svelte for VSCode extension`:
 
 ```json
   "[svelte]": {

docs/internal/deployment.md

@@ -2,13 +2,13 @@
 
 The [publisher is Svelte](https://marketplace.visualstudio.com/manage/publishers/svelte)
 
-- Extension builds with the account signed up via GitHub from orta
+-   Extension builds with the account signed up via GitHub from orta
 
 ### npm deployments
 
-- Deployments come from a bot: `svelte-language-tools-deploy`
+-   Deployments come from a bot: `svelte-language-tools-deploy`
 
 ### When Deployments happen
 
-- Nightly builds are triggered through a scheduled GitHub workflow every night at 04:00 UTC.
-- Production builds are triggered by creating a new tag, which is best done through the "do a release" on Github. The tag name equals the version that is then shown on the marketplace, so each tag should have a higher version than the previous.
+-   Nightly builds are triggered through a scheduled GitHub workflow every night at 04:00 UTC.
+-   Production builds are triggered by creating a new tag, which is best done through the "do a release" on Github. The tag name equals the version that is then shown on the marketplace, so each tag should have a higher version than the previous.

docs/internal/overview.md

@@ -52,7 +52,7 @@ We chose the second option because TypeScript provides a language service which
 
 `svelte2tsx` uses some [ambient definitions](/packages/svelte2tsx/svelte-shims.d.ts) which are loaded by the language server to do some of the transformations. It also provides [JSX definitions](/packages/svelte2tsx/svelte-jsx.d.ts) which are recognized by the TypeScript compiler and define intrinsic elements, attributes and events - so if you ever get an error that a DOM attribute is not assignable to a DOM element, it's likely a missing declaration in there.
 
-The code generated by `svelte2tsx` is not runnable in any way and does not actually exist at runtime when you run your app, it purely exists for the IntelliSense. 
+The code generated by `svelte2tsx` is not runnable in any way and does not actually exist at runtime when you run your app, it purely exists for the IntelliSense.
 
 The code also returns source mappings so we know which position in the original code corresponds to which generated position.
 

docs/preprocessors/in-general.md

@@ -4,14 +4,14 @@
 
 If a svelte file contains some language other than `html`, `css` or `javascript`, `svelte-vscode` needs to know how to [preprocess](https://svelte.dev/docs#svelte_preprocess) it. This can be achieved by creating a `svelte.config.js` file at the root of your project which exports a svelte options object (similar to `svelte-loader` and `rollup-plugin-svelte`). It's recommended to use the official [svelte-preprocess](https://github.com/sveltejs/svelte-preprocess) package which can handle many languages.
 
-> NOTE: you __cannot__ use the new `import x from y` and `export const` / `export default` syntax in `svelte.config.js`.
+> NOTE: you **cannot** use the new `import x from y` and `export const` / `export default` syntax in `svelte.config.js`.
 
 ```js
 // svelte.config.js
 const sveltePreprocess = require('svelte-preprocess');
 
 module.exports = {
-    preprocess: sveltePreprocess(),
+    preprocess: sveltePreprocess()
 };
 ```
 
@@ -46,9 +46,9 @@ const sveltePreprocess = require('svelte-preprocess');
 module.exports = {
     preprocess: sveltePreprocess({
         defaults: {
-            script: 'typescript', // <-- now you can just write <script>let typingsAllowed: string;</script>
-        },
-    }),
+            script: 'typescript' // <-- now you can just write <script>let typingsAllowed: string;</script>
+        }
+    })
 };
 ```
 
@@ -63,14 +63,14 @@ const sveltePreprocess = require('svelte-preprocess');
 // using sourceMap as an example, but could be anything you need dynamically
 function createPreprocessors(sourceMap) {
     return sveltePreprocess({
-        sourceMap,
+        sourceMap
         // ... your settings
     });
 }
 
 module.exports = {
     preprocess: createPreprocessors(true),
-    createPreprocessors,
+    createPreprocessors
 };
 ```
 
@@ -88,10 +88,10 @@ export default {
         // ...
         svelte({
             // ...
-            preprocess: createPreprocessors(!production),
-        }),
+            preprocess: createPreprocessors(!production)
+        })
         // ...
-    ],
+    ]
 };
 ```
 

docs/preprocessors/scss-less.md

@@ -27,7 +27,7 @@ You need a `svelte.config.js`. [Read here on how to set it up and also how it re
 const sveltePreprocess = require('svelte-preprocess');
 
 module.exports = {
-    preprocess: sveltePreprocess(),
+    preprocess: sveltePreprocess()
 };
 ```
 
@@ -76,6 +76,6 @@ const sveltePreprocess = require('svelte-preprocess');
 const path = require('path');
 
 module.exports = {
-   preprocess: sveltePreprocess({ includePaths: [path.join(__dirname, 'relative/path')] })
+    preprocess: sveltePreprocess({ includePaths: [path.join(__dirname, 'relative/path')] })
 };
 ```

docs/preprocessors/typescript.md

@@ -32,7 +32,7 @@ You may optionally want to add a `svelte.config.js` file - but it is not require
 const sveltePreprocess = require('svelte-preprocess');
 
 module.exports = {
-    preprocess: sveltePreprocess(),
+    preprocess: sveltePreprocess()
 };
 ```
 

package.json

@@ -12,10 +12,10 @@
         "build": "tsc -b",
         "test": "CI=true yarn workspaces run test",
         "watch": "tsc -b -watch",
-        "lint": "eslint \"packages/**/*.{ts,js}\""
+        "format": "prettier --write .",
+        "lint": "prettier --check . && eslint \"packages/**/*.{ts,js}\""
     },
     "dependencies": {
-        "axios": "0.21.1",
         "typescript": "^4.1.3"
     },
     "devDependencies": {
@@ -24,6 +24,7 @@
         "@typescript-eslint/parser": "^4.3.0",
         "eslint": "^7.7.0",
         "eslint-plugin-import": "^2.22.1",
-        "eslint-plugin-svelte3": "^2.7.3"
+        "eslint-plugin-svelte3": "^2.7.3",
+        "prettier": "2.2.1"
     }
 }