[TypeScript] index.d.ts not copied under `node_modules/react-json-view/`
See original GitHub issueAfter pulling the latest version (1.16.2), I still don’t see index.d.ts
under node_modules/react-json-view/
, nor is it under dist
. Is there any steps missing? Could you look into this?
Issue Analytics
- State:
- Created 5 years ago
- Comments:24 (12 by maintainers)
Top Results From Across the Web
TypeScript `.d.ts` file not copied to output, causing broken ...
Based on this issue (found in a web search), the behavior is intentional and I don't think there's another solution than renaming index.d.ts...
Read more >Typescript error: index.d.ts file is missing · Issue #147 - GitHub
After upgrading the library from 1.2.3 to 1.2.5 I started to see hookrouter/dist/index.d.ts is not a module error. I think it's because *.d.ts...
Read more >Documentation - Modules .d.ts - TypeScript
Create an index.d.ts in that folder, and copy the example in; See where your usage of the module breaks, and start to fill...
Read more >Module Resolution - TypeScript
If that didn't work and if the module name is non-relative (and in the case ... /root/node_modules/@types/moduleB.d.ts; /root/node_modules/moduleB/index.ts ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
the deed is done! 🙌 https://unpkg.com/react-json-view@1.16.5/
the
files
key inpackage.json
was gating my published files to only include/dist/
(and a few other whitelisted files). Now.npmignore
should be the only files missing from the published module. see diff here: https://github.com/mac-s-g/react-json-view/commit/1ab70e2668837872e8db2a0ebfd996bcd5edcc11thanks for working through that with me @franklixuefei ! let me know if 1.16.5 is working for you, so I can close this issue.
fix is merged and published under 1.16.6