non25

https://github.com/firefish5000/svelte-trim Can we adopt something like this in the compiler? A customizable solution, which will avoid generating AST twice. It will improve DX a lot.

I've examined `~/.yarn/berry/telemetry.json`, the content is mostly fine, but I feel you should omit saving directories. ```json "enumerators": { "projectCount": [ "/tmp/webpack-virtual-modules" ] }, ``` I find that unacceptable and...

@AustinGil maybe you will find this approach helpful: https://github.com/sveltejs/svelte-loader/pull/151

Here's some observations too: I've put `console.log`s everywhere, where `fileTimestamps` are getting recreated from scratch. ``` > grep -nr 'fileTimestamps =' lib/Watching.js:134: this.compiler.fileTimestamps = fileTimestamps; lib/Watching.js:153: this.compiler.fileTimestamps = this.watcher.getFileTimestamps(); lib/WatchIgnorePlugin.js:77:...

@dummdidumm I too decided to try `neovim-lsp`, and it works brilliantly even with zip-packed yarn 2 packages, thanks to overridable cmd option: ```lua lspconfig.tsserver.setup{ cmd = { "yarn", "typescript-language-server", "--stdio"...

So using onwarn in it's current form is acceptable direction to go ? To be compatible with existing configs, we could implement similar onwarn callback interface for intercepting warnings like...

I have prettier as a pre-commit hook. Configuration is in `package.json`. ```json { "prettier": { "singleQuote": true, "printWidth": 80, "plugins": [ "prettier-plugin-svelte" ] } } ``` Is there something special...

I agree, now I don't see anything else other than `onwarn` to reasonably move to the `svelte.config.js`. There's not much to decide left. Do making `onwarn` callback in every tool...

So the solution is: 1. Teach my LS client to read config files from the workspace and pass configuration to the LS like `svelte-vscode` does. 2. Import configuration from `svelte.config.js`...

I'd just use `patch-package`. It's more productive. :grin: