Skip to content
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

Note about "parserOptions.project" error #627

Closed
wants to merge 1 commit into from

Conversation

devinrhode2
Copy link
Contributor

No description provided.

@sindresorhus
Copy link
Member

This should to be required. This seems like a regression caused by #622.

Do you have any place we can reproduce it?

// @spence-s

@spence-s
Copy link
Contributor

Filed an issue for this #629 - can work on this later today. Not exactly sure best way to fix right now. It's difficult to know what files are covered by ts configs, but I think it's worth staying away from caching a tsconfig for each file as what was happening before.

@spence-s
Copy link
Contributor

I think we may be able to resolve this nicely by using ts API to resolve the tsconfig over cosmic config. Ts can tell us when we can/can't resolve a config for a file correctly.

@devinrhode2
Copy link
Contributor Author

Sorry guys been an interesting last couple weeks
@spence-s - is this documentation change made irrelevant by your recent PR?

@spence-s
Copy link
Contributor

@devinrhode2 yes - this documentation is not needed. Assuming everything is working correctly you should never get this error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants