Cli package
option creates skeleton library project with missing configuration file
#9711
Labels
bug
Something isn't working
Describe the bug
It looks like if you elect to use neither JS with types or Typescript when creating a package from the CLI, you end up without a jsconfig or tsconfig file.
However, packaging defaults types to true, because it's recommended for the ecosystem, so this file is mandatory.
Reproduction
Logs
System Info
Severity
annoyance
Additional Information
No response
The text was updated successfully, but these errors were encountered: