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

refactor: make our full set of typings mutually compatible #2617

Merged
merged 1 commit into from
Apr 21, 2021

Conversation

alexeagle
Copy link
Collaborator

By not installing @types/jest and @types/jasmine together, we avoid TS having type conflicts when running outside the sandbox.
This makes it a lot easier to make compiles succeed on windows for example, which trips a lot of first-time contributors

By not installing @types/jest and @types/jasmine together, we avoid TS having type conflicts when running outside the sandbox.
This makes it a lot easier to make compiles succeed on windows for example, which trips a lot of first-time contributors
@alexeagle alexeagle merged commit 00b5afd into bazel-contrib:stable Apr 21, 2021
@alexeagle alexeagle deleted the types_simpler branch April 21, 2021 19:53
twheys pushed a commit to twheys/rules_nodejs that referenced this pull request Jan 13, 2022
…trib#2617)

By not installing @types/jest and @types/jasmine together, we avoid TS having type conflicts when running outside the sandbox.
This makes it a lot easier to make compiles succeed on windows for example, which trips a lot of first-time contributors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants