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
The issue here is that we only including node_modules in the current folder for automatic type discovery. this causes a lot of confusion for users trying to use the new @types package, specially if they are global. ppl do not usually associate the location of their tsconfig.json with it not working, all they see is that sometimes it does and sometimes it does not.
The text was updated successfully, but these errors were encountered:
Worth noting that TypeScript already searches up through containing folders for typings that are bundled into their modules, i.e. modules whose package.json uses the "typings" field.
And of course the runtime behaviour with node_modules is to search up through containing folders too.
For example the following very similar example works. The difference is that the @cycle/dom module bundles its own typings. In this case TypeScript does search containing directories.
The issue here is that we only including node_modules in the current folder for automatic type discovery. this causes a lot of confusion for users trying to use the new
@types
package, specially if they are global. ppl do not usually associate the location of their tsconfig.json with it not working, all they see is that sometimes it does and sometimes it does not.The text was updated successfully, but these errors were encountered: