Change our js/ts/npm build config to get types working in downstream projects #78
Commits on Jan 29, 2024
-
Adjust the package.json and tsconfig.json that sknpm produces and uses
The goal: get declaration files working so that we get typing information for downstream projects. Why these settings? Because typescript docs tell me to: https://www.typescriptlang.org/docs/handbook/modules/guides/choosing-compiler-options.html And they work! And I tried a _lot_ of things that didn't until I found these docs.
-
-
Do not massage declaration import paths
These are now correctly produced and work. But the path stuff does still need to be stripped. It is not supported and requires downstream projects to also define the paths. Refer: https://stackoverflow.com/a/52501384 microsoft/TypeScript#15479
-
Replace all import paths in runtime files .js -> .mjs
We rename the extension when copying runtime js files over, so we need to massage the imports/exports to comply.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.