Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we improve the generation of .tsconfig.json for new pepr modules? #1814

Open
samayer12 opened this issue Feb 12, 2025 · 0 comments
Open
Labels
question Further information is requested SPIKE

Comments

@samayer12
Copy link
Contributor

Research Goal

Pepr contains four tsconfig.json files:

./tsconfig.eslint.json
./tsconfig.json
./src/templates/tsconfig.module.json
./src/templates/tsconfig.json

Two of them appear to be used during pepr init (see src/cli/init/templates.ts). The presence of multiple files creates room for configuration drift. We should seek to answer the following questions:

  • Why do we have four files that match the pattern tsconfig.*.json?
  • How is the exported variable tsConfig (see templates.ts) used in generating new pepr modules?
  • Can we derive the tsconfig.json file used in new pepr modules from the ./tsconfig.json file used by Pepr?

Definition of Done

We'll know we're done with this spike when we can answer the above questions and link to any follow-on issues created from this spike.

@samayer12 samayer12 added question Further information is requested SPIKE labels Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested SPIKE
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant