Typescript Compliance

[kanthesha]

We want to make sure that for a given project:

• The project contains a tsconfig.json file, and the content of the file matches the same file in the module template
• The project contains a tsconfig.build.json file, and the content of the file matches the same file in the module template
• The project contains a tsup.config.ts file, and the content of the file matches the same file in the module template
• The project contains @types/node, ts-node, tsup, and typescript as dev dependencies, and the versions match the same dev dependencies as in the module template
• The project contains the same build and build:types package scripts as in the module template
• The project's package.json has an exports field, and all of the keys in exports should be present in the project's exports field and the values should match.
• The project's package.json has a main field, and its value should match the same field in the module template.
• The project's package.json has a module field, and its value should match the same field in the module template.
• The project's package.json has a types field, and its value should match the same field in the module template.
• The project's package.json has a files field, and its value should match the same field in the module template. If project's package.json contains a lavamoat field, and that contains allowScripts, then a tsup>esbuild property should be present and should match the same one in the module template.

Fixes #8

[socket-security[bot]]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

[socket-security[bot]]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/lodash@4.14.202	None	0	862 kB	types

View full report↗︎