chore: add typescript declarations to .gitignore

[boneskull]

When npm-link-ing Endo against external projects, the types are not resolvable without first building the declaration files (unlike how types are resolved within the project itself). This requires compiling declaration files in the appropriate Endo workspaces and re-running as needed.

Previously, all generated declaration files (and their sourcemaps) were recognized as unstaged new files by Git, which is incredibly annoying when trying to see what changes have been made to Endo sources.

This change adds declaration files, their sourcemaps and any build cache files (*.tsbuildinfo) to Git's ignorelist.

Caveats:

• Any future declaration files which need to be under version control must be force-added
• When publishing, npm's default behavior is to skip ignored files unless they are present in a package.json's files array. I believe this is already configured correctly, but future packages must maintain the same strategy. I recommend carefully examining the output of npm pack --dry-run before the next publish to avoid regressions in the list of published artifacts.

---

An example of my workflow is something like this:

npm link -w @endo/compartment-mapper \
  -w ses \
  -w @endo/env-options \
  -w @endo/cjs-module-analyzer \
  -w @endo/static-module-record \
  -w @endo/zip \
  -w @endo/evasive-transform
cd /path/to/lavamoat
npm link @endo/compartment-mapper \
  ses \
  @endo/env-options \
  @endo/cjs-module-analyzer \
  @endo/static-module-record \
  @endo/zip \
  @endo/evasive-transform

At this point, my build will fail because the type declarations I need are missing. So I need to:

cd /path/to/endo
npm run prepack -w @endo/compartment-mapper -w ses

This will generate the declarations I need, but git status results in:

...
?? packages/compartment-mapper/src/policy.d.ts
?? packages/compartment-mapper/src/policy.d.ts.map
?? packages/compartment-mapper/src/powers.d.ts
?? packages/compartment-mapper/src/powers.d.ts.map
?? packages/compartment-mapper/src/search.d.ts
?? packages/compartment-mapper/src/search.d.ts.map
?? packages/compartment-mapper/src/types/compartment-map-schema.d.ts
?? packages/compartment-mapper/src/types/compartment-map-schema.d.ts.map
?? packages/compartment-mapper/src/types/external.d.ts
?? packages/compartment-mapper/src/types/external.d.ts.map
?? packages/compartment-mapper/src/types/internal.d.ts
?? packages/compartment-mapper/src/types/internal.d.ts.map
?? packages/compartment-mapper/src/types/node-powers.d.ts
?? packages/compartment-mapper/src/types/node-powers.d.ts.map
?? packages/compartment-mapper/src/types/policy-schema.d.ts
?? packages/compartment-mapper/src/types/policy-schema.d.ts.map
?? packages/compartment-mapper/src/types/policy.d.ts
?? packages/compartment-mapper/src/types/policy.d.ts.map
?? packages/compartment-mapper/src/types/powers.d.ts
?? packages/compartment-mapper/src/types/powers.d.ts.map
?? packages/compartment-mapper/src/types/typescript.d.ts
?? packages/compartment-mapper/src/types/typescript.d.ts.map
?? packages/compartment-mapper/src/url.d.ts
?? packages/compartment-mapper/src/url.d.ts.map
?? packages/compartment-mapper/tsconfig.build.tsbuildinfo

...which is annoying if I have actual changes in Endo!

[boneskull]

(Yes, this change is basically just for me)

[mhofman]

We have a lot of manually authored .d.ts files so a blanket ignore of them is not ok. In general I wish we had a CI job to verify that any files in the repo are not currently excluded by the gitignore config, as it's a pain to manage files "force added"

[mhofman]

• When publishing, npm's default behavior is to skip ignored files unless they are present in a package.json's files array. I believe this is already configured correctly, but future packages must maintain the same strategy. I recommend carefully examining the output of npm pack --dry-run before the next publish to avoid regressions in the list of published artifacts.

I believe @kriskowal has some commands to verify no regression here that I'd like to see the output of before approving a merge.
Basically list all the files in packed packages before and after, and diff the lists.

[boneskull]

@mhofman I feel like the concern may be overblown.

git ls-files '*.d.ts'
packages/bundle-source/src/exports.d.ts
packages/captp/src/ts-types.d.ts
packages/cli/test/_types.d.ts
packages/compartment-mapper/src/types-external.d.ts
packages/compartment-mapper/src/types.d.ts
packages/daemon/src/types.d.ts
packages/daemon/types.d.ts
packages/eventual-send/src/exports.d.ts
packages/eventual-send/src/types.d.ts
packages/exo/src/types.d.ts
packages/far/src/exports.d.ts
packages/lp32/types.d.ts
packages/pass-style/src/types.d.ts
packages/ses/src/reporting-types.d.ts
packages/ses/types.d.ts
packages/stream/types.d.ts
packages/trampoline/types.d.ts
packages/where/types.d.ts

We aren't really adding a ton of these on a regular basis.

[boneskull]

This should surface everything to be published:

npm pack --workspaces --json --dry-run

So we can diff the output of that

[turadg]

One way forward is to have a consistent module name for hand-written types and make that an exclusion in gitignore.

[boneskull]

Some tests are failing because git clean -f '*.d.ts' doesn't work anymore. 😄

tsc --clean should be a workable replacement in most cases.

UPDATE: git clean -fX is what we want now

[boneskull]

@turadg Since I was touching the postpack scripts, I noticed that some of them are git clean -f '*.d.ts*' '*.tsbuildinfo' and others are git clean -f '*.d.ts*'; should all of them be the former?

[mhofman]

As @turadg mentioned, while we may not have a lot of these manual definition files currently, I would really like them to be excluded one way or another from being ignored. Force added files are a pain to deal with.

[kriskowal]

Per @turadg and @mhofman’s concern about force-adding, I propose we arrive at a naming convention for hand-written type definitions. .gitignore supports a ! negation prefix that we can use to override the above general rules.

*.d.{m,c,}ts*
!types*.d.{m,c,}ts
!types/*.d.{m,c,}ts