Update FURN builds to use node16 module resolution and export maps #3923
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.
Platforms Impacted
Description of changes
Additional Updates 7/3
Some more changes to fix issues with the bundles.
The way TS was set up in fluent-tester, reaching across to the e2e package, caused TS to create a lib structure with lib/e2e/src and lib/fluent-tester/src within the fluent-tester package. It's causes wonky behavior, adding as a reminder to folks to not do this.
Original Description
To update FURN to use the modern jsx runtime it needs to use more modern settings, in particular export maps, which require using node16. This caused a bit of a cascade:
Verification
Normal build and pipeline runs.