When a new pilet is scaffolded using npm init pilet@latest the generated (via postinstall) declaration is empty (expected) and located in the project's root folder (instead of the dist) folder. I thin this only happens on scaffolding.
Steps to Reproduce
Scaffold a new pilet
Look in the pilet's root folder
Expected behavior
Either nothing (since the pilet.d.ts is anyway empty) should be generated, or an empty file in the dist folder.
Actual behavior
The file is generated in the root folder.
Possible Origin/Solution
I think that the dist is not yet given as the previous "version" of the package.json did not have a proper main specified. Thus, it falls back to the root directory.
Bug Report
For more information, see the
CONTRIBUTINGguide.Prerequisites
Environment Details and Version
Ubuntu, Piral CLI 1.4.1
Description
When a new pilet is scaffolded using
npm init pilet@latestthe generated (viapostinstall) declaration is empty (expected) and located in the project's root folder (instead of thedist) folder. I thin this only happens on scaffolding.Steps to Reproduce
Expected behavior
Either nothing (since the pilet.d.ts is anyway empty) should be generated, or an empty file in the
distfolder.Actual behavior
The file is generated in the root folder.
Possible Origin/Solution
I think that the dist is not yet given as the previous "version" of the package.json did not have a proper
mainspecified. Thus, it falls back to the root directory.