You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I use TS version 2.2.2 for instance in my project, and install testcafe, which has ^ in typescript package version ( which will install latest version till 3 ), my whole build will start to break, because testcafe's TS dependency overrides my older version -> what does it mean?
node_modules/.bin/tsc -> will symlink to testcafe/node_modules/typescript,
so when I run yarn tsc during my build tsc version 2.4.2 will run ( which had breaking changes by means of stricter type checking ) and my build will not pass, which is very unfortunate
Testcafe has ^2.2.2 version specified in package.json, which means it will install latest 2.x.x and never any other major version. Also, package manager shouldn't override binary bindings in project root node_modules with transitive dependency version if their semver range doesn't overlap. So, it's either bug in yarn or something is wrong with your project configuration.
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.
Are you requesting a feature or reporting a bug?
none of them, rather a build change
What is the current behavior?
If I use TS version 2.2.2 for instance in my project, and install testcafe, which has
^
in typescript package version ( which will install latest version till 3 ), my whole build will start to break, becausetestcafe's
TS dependency overrides my older version -> what does it mean?node_modules/.bin/tsc -> will symlink to testcafe/node_modules/typescript,
so when I run
yarn tsc
during my build tsc version2.4.2
will run ( which had breaking changes by means of stricter type checking ) and my build will not pass, which is very unfortunatesimilar issue like
TypeStrong/typedoc#556
What is the expected behavior?
making typescript peerDependency or fixing version in dependencies to oldest possible.
Specify your
The text was updated successfully, but these errors were encountered: