MichalLytek / MichalLytek/typegraphql-prisma
publish to `node_modules/.cache/typegraphql` instead of `@generated/typegraphql`
- Dominant language
- TypeScript
- Stars
- 918
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Unrelated npm script calls seem to affect `@generated/typegraphql` resources. I might be mistaken, but vscode frequently seems to lose its contents.
Anyway, I think it is more in line with node package publish best practices to use `node_modules/.cache/*` instead of `@generated/*`. I believe the `.cache` folder is guaranteed to not be erased.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named. Start by tracing where the Prisma generator writes @generated/typegraphql resources and how npm package output is configured. Done means generated resources use node_modules/.cache/typegraphql and the reported effects from unrelated npm scripts are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100