chore: use Node16
and add extensions to all relative imports
#28
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.
This PR is a prerequisite to adding the adder templates into the repo.
While working on migrating over the templates, I noticed that none of the types from the core package were resolving correctly in the adder templates due to our lack of file extensions in relative imports (since we had
moduleResolution
set toBundler
, it allowed us to have a mix of imports with and without extensions, causing things to break for projects that usemoduleResolution: Node16
).Since this is will also be needed for Rolldown in the future, we might as well get this out of the way