-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors while linting TypeScript #108
Comments
I guess you forgot |
Is this package expected to work with TypeScript or not? I assumed it was because it includes |
it works in my case, what's your typescript and prettier-standard version in package.json? how do you run it? |
You are correct. I figured out that my issue was with eslint. |
I'm having the same issues as the OP. There's actually a couple of different scenarios: Combinations of:
or
Results in eslint parsing errors. Rolling back to 16.3.0 resolves my issue. |
Encountered the same problem today, and can also confirm rolling back to 16.3.0 seems to resolve it. In my case it seems to be choking on this: export type ThrowableType = new () => Error Which results in:
This behavior can be observed in the public repo I'm working in here (running |
Note that the version is specifically 16.3.0 because in the latest version (16.4.1 when doing this commit) TypeScript support seems broken. See sheerun/prettier-standard#108.
Came here because of the same types of problems.
or
or
problems occur with All of them go away when you revert to |
When setting
Rolling back to |
solved the optional chaining problem by replacing dependency "prettierx"(0.11 in package) to newest version(currently 0.17). You can try if it could solve other problems. |
This is pretty old and I'm running into the same problem. Rolling back to 16.3.0 definitely fixed the issue for me. |
@HoraceShmorace this library doesn't seem to be maintained anymore |
I've installed
prettier-standard
to my monorepo project. When I runprettier-standard --lint
on the root, I get the following errors:Am I missing something?
The text was updated successfully, but these errors were encountered: