default-index.d.ts is outdated
See original GitHub issuehttps://github.com/prisma/prisma/blob/master/src/packages/client/scripts/default-index.d.ts is outdated in comparison to the fully generated version:
- Code example in docs comment
- Documentation link in docs comment
- Possibly missing namespace for property dmmf?
- Line breaks for
PromiseType
andPromiseReturnType
Found via comparing node_modules\.prisma\client\index.d.ts
in a project before and after generating a Client the first time.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
TypeScript error in bridge.d.ts and analytics.d.ts #11 - GitHub
I recently stumbled upon the following error when running tsc in my project: node_modules/@segment/analytics-react-native/build/esm/analytics.d.
Read more >TypeScript typings give me "index.d.ts is not a module"
The index.d.ts file indeed is not a module, it just references two other files with interfaces in them. So I thought to remove...
Read more >How Jotai Specifies Package Entry Points - Daishi Kato's blog
Old Node.js works with this and maybe old bundlers do too. ... far as I understand, tsc looks for the same file name...
Read more >Typescript | Kibana Guide [7.17] - Elastic
Every project emits public interfaces in the form of d.ts type ... how your changes affect tsc compiler performance with node --max-old-space-size=4096 ....
Read more >dts-umd-webpack-plugin - npm Package Health Analysis - Snyk
Configuration. First, import your plugin in old way const DefinitionBundlePlugin = require('dts-umd-webpack-plugin').DefinitionBundlePlugin;.
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
This seems to be working nicely for me:
Prisma
namespaceimport { Prisma } from "@prisma/client";
- the namespace itself seems to be a named exportPrisma.PromiseReturnType
🙏
@jasonsilvers Sounds unrelated. Can you please open a new issue with the usage which you are doing?