Stephan Meijer - When exporting myschema's and ...
When exporting my schema's as a package and then importing them, I get errors...
and
for example in
The package '@toegang-voor-iedereen/document-spec-types' can be found here:
- https://gitlab.com/toegang-voor-iedereen/specification/types/typescript
- https://gitlab.com/toegang-voor-iedereen/specification/types/typescript/-/packages
Solution:Jump to solution
The basic issue is that typescript-eslint is getting an error from its own internal typescript compiler message. Usually restarting can help, but if it persists there might be a configuration issue in eslint or in the ide plugin
16 Replies
The package is installable by creating
.npmrc with contents
this sounds like eslint cannot get the type of the function correctly. most likely a eslint config issue.
this is a variation on this problem that pops up from time-to-time on typescript-eslint: https://github.com/typescript-eslint/typescript-eslint/issues/9771
GitHub
Bug: [no-unsafe-assignment] "Unsafe assignment of an error typed va...
Before You File a Bug Report Please Confirm You Have Done The Following... I have tried restarting my IDE and the issue persists. I have updated to the latest version of the packages. I have search...
Thanks. That sounds very vague. What can one do about it?
Have you tried restarting the eslint lap server?
I didn't mean your explanation was vague btw, but the error is
Will try tomorrow to pry a bit into it
Thanks for your help on this, appreciate it!
Solution
The basic issue is that typescript-eslint is getting an error from its own internal typescript compiler message. Usually restarting can help, but if it persists there might be a configuration issue in eslint or in the ide plugin
I want to write a blog post about this but I think it'll be a little bit better by the time I get around to writing it.
Sounds buggy, if this is an IDE thing I will be switching editors.
Let me know if I can contribute on that
It's a typescript-eslint thing, especially the type-checking lint rules that runs its own compilation so it can be out of sync with, for instance, the LSP instance.
Sounds buggy
The eslint world is in a bit of a rough place right now, especially the typescript-eslint world. Next year maybe?
I have a lot of trust in the maintainers of those tools that they'll work it out soon, though. It's a tough problem especially with the new flat config, and things like typescript project references
Probably everything in the realm of static analysis and compiling stuff is quite tough
Can't even wrap my head around the complexity that goes into writing those programs like eslint, typescript and typescript-eslint
I have a suspicion that typescript-eslint and vscode-eslint are going to get it working soon, tbh. They're actively working on it
Yeah btw this is Jetbrains
Maybe VScode will give me better results
Maybe! But the type-enabled rules in typescript-eslint are tough in-general for a long running thing like a language server. They'll figure it out though, I trust