Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
TypeScript Definitions Issue
See original GitHub issueBecause of the recent change in TypeScript definitions (from namespace to type) in https://github.com/nbubna/store/commit/1ca5d1605bfdd8f1662317e8f7182f91d5075439, the package is now broken for TypeScript users. I’ve confirmed that store.set() and store.get() work as usually in JavaScript, but because store is now a type in the TS definitions, it can’t be used the same way. (Since our project is written in TS, the latest version of store breaks our builds.)
Is there a change to how we’re supposed to handle the package in TS? Or is this a bug? Either way, would really appreciate some help here.
Thank you!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:21 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok, 2.13.1 has been published. Thank you, again, for the help with this one! And sorry for the trouble.
Thank you, shirblc, for the test repo! And being willing to test. I think i was able to test too, using your repo. I checked it out was able to get the error, then manually tweak the store2 index.d.ts as i show above in the node_modules directory, and ran tsc again. It seems like it does the trick. So i think we’re good. I’ll get a bugfix release out asap.