Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Fix Types not Resolving in Node ESModule projects #2184
Conversation
josh-hemphill
changed the title
|
Does it actually require the filename? If so, how was this even working in the first place? |
|
Sorry, I though the problem might just be my configuration, but It's gone full circle now, and nothing I've been able to do has gotten me intellisense/type completion. |
EsModule imports do not automatically resolve index files of directories, so the
"types": "types"does not resolve to thetypes/index.d.tsas was intended. If it doesn't break anything, it should be changed to"types": "types/index.d.ts".According to the Typescript Spec, the types/typings field should be a file, not a directory.