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
Type dependencies are not always consistent within a build, and sometimes change over time for a given build of a package. I have mostly seen this problem with react and react-dom, which will sometimes use different type dependencies for the same packages, even when pinned.
The versions for @types/react are different for the react and react-dom dependencies, causing errors while type checking. Type dependencies can also change when new builds are published, even when a project has pinned dependencies, meaning that a build that works on one machine may break when run on another due to different package versions being downloaded.
The text was updated successfully, but these errors were encountered:
Type dependencies are not always consistent within a build, and sometimes change over time for a given build of a package. I have mostly seen this problem with react and react-dom, which will sometimes use different type dependencies for the same packages, even when pinned.
This may be related to #234.
For example, in a current project I'm importing build 68 of react and react-dom:
If I run
deno info mod.ts
for my project, I see the following imports for react:And for react-dom:
The versions for @types/react are different for the react and react-dom dependencies, causing errors while type checking. Type dependencies can also change when new builds are published, even when a project has pinned dependencies, meaning that a build that works on one machine may break when run on another due to different package versions being downloaded.
The text was updated successfully, but these errors were encountered: