Unused export property warning is on the wrong line when using the TypeScript pre-processor.
See original GitHub issueDescribe the bug
export let
statements of an unused property cause a warning. The warning is displayed on the line above the actual property for me.
To Reproduce
Set the script language to typescript (lang="ts"
or type="text/typescript"
).
Declare some export property, do not use it anywhere.
Expected behavior
The warning is on the property not being used.
Screenshots
If the property is in the first line of the script:
System (please complete the following information):
- OS: Windows 10, 64bit
- IDE: VSCode
- Plugin/Package: Svelte for VSCode
Issue Analytics
- State:
- Created 3 years ago
- Comments:18 (11 by maintainers)
Top Results From Across the Web
Suppress unused property warning in Typescript for individual ...
Is there a way to let my code compile with ts-node even if there is unused property warnings in one ...
Read more >svelte-check - npm
svelte-check needs to know the whole project to do valid checks. Imagine you alter a component property export let foo to export let...
Read more >PyCharm 181.4203.547 Release Notes | Knowledge Base
Feature PY‑20770 Support Python 3.6 asynchronous generators and comprehensions
Feature PY‑21768 Semantic highlighting for Python
Bug PY‑19573 Python console ‑ no output under OS X
Bug...
Read more >Configuring Jest
The configuration file should simply export an object: JavaScript; TypeScript. /** @type {import('jest').Config} */ const config = {
Read more >Code Splitting - webpack
Prevent Duplication: Use Entry dependencies or SplitChunksPlugin to dedupe and split chunks. Dynamic Imports: Split code via inline function calls within ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing as these are problems related to
svelte-preprocess
. The “source map is not applied when I tell preprocess through its sourceMap-option”-problem is fixed in the latest version. The “extends
-feature oftsconfig.json
not supported” is tracked in https://github.com/sveltejs/svelte-preprocess/issues/300 .Yeah, I have a quick look at the source file of the svelte-preprocess. It looks like it doesn’t parse the
extends
. Thanks for the issue!