Missing Typescript declarations for next-slicezone
See original GitHub issueVersion
v3.8.4
Reproduction
- install
next-slicezone
in a Typescript project. - import hooks.
What is expected?
- A TypeScript definition is found for all importable modules.
What is actually happening?
- The TypeScript compilator complains (and refuses to compile).
Any additional information
Auto-generated declarations should probably cover most needs. https://www.typescriptlang.org/docs/handbook/declaration-files/dts-from-js.html
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:8 (2 by maintainers)
Top Results From Across the Web
How to type new prismic SliceZone components
I wanted to replace the next/slicezone with the new slicezone. But I ran into TypeScript problems. All my slice components are typed like...
Read more >Missing typescript declaration file in javascript - Stack Overflow
My project is mixed javascript and typescript files. That's my tsconfig.json file: "compilerOptions": { "target": "es2017", "baseUrl": ".
Read more >@prismicio/react | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >next-slicezone - npm
Next SliceZone. A component that fetches Prismic files, returns slices found and matches them with front-end components.
Read more >GEOM User Guide - LLNL - Nuclear Data
All base names may cg be displayed with command "last". cg The next name after or ... See a math or geometry handbook...
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
any fix? that library needs type declaration file
Yep, you’d want to do something like the following for the time being
Also, to avoid the eslint error
react-hooks/rules-of-hooks
you’d want to alias the “useXXX” exports