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
As @types/react is set as dependency i'm having issues with typescript check on my react-native application.
Seems that, by adding the definition inside the dependencies instead of the devDependencies in simple-makrdown, after installing the package now @types/react becomes an active dependency on my project as well, and all react types start to apply globally on my tsc check.
Can you please move it do devDependency?
The text was updated successfully, but these errors were encountered:
@Apexal i will definitely check that.
But i believe my issue is slightly different. Before installing the package, those dependencies are tagged as dev dependencies, and TS check does not threat them as global types by default, which is the case after installing this package. Those dependencies switch from dev to normal, and TS includes them by default.
Maybe this can be solved by some customisation on the tsconfig file. But still, there is no need to have them as dependencies in this package IMO.
As @types/react is set as dependency i'm having issues with typescript check on my react-native application.
Seems that, by adding the definition inside the dependencies instead of the devDependencies in simple-makrdown, after installing the package now @types/react becomes an active dependency on my project as well, and all react types start to apply globally on my tsc check.
Can you please move it do devDependency?
The text was updated successfully, but these errors were encountered: