I observe an incorrect behavior: generating declarations[^dts-name] changes structure entirely based on the presence of a single file. This makes predictability hard with the package.json#exports:
[^dts-name]: Note that dist-types was an old name for the declarations directory for the v2 addon blueprint. This has no impact on any one's code, because the mapping is defined by the package.json#exports, but the v2 addon blueprint now using the declarations folder name.
I observe an incorrect behavior: generating declarations[^dts-name] changes structure entirely based on the presence of a single file. This makes predictability hard with the
package.json#exports
:Before: https://stackblitz.com/edit/ember-cli-editor-output-6bfkuh?file=README.md With the following file structure:
And this tsconfig.json:
the following declarations directory is created:
Real output from the above stackblitz:
After: https://stackblitz.com/edit/ember-cli-editor-output-unnbr3 The only change:
src/index.ts
now the dist-types directory is correct
Real output for the above stackblitz:
[^dts-name]: Note that dist-types was an old name for the declarations directory for the v2 addon blueprint. This has no impact on any one's code, because the mapping is defined by the
package.json#exports
, but the v2 addon blueprint now using thedeclarations
folder name.