feat(test-ssr): add custom esbuild-plugin to properly resolve TS path aliases which stopped working starting esbuild 0.19 #31227
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.
Previous Behavior
Esbuild stopped resolving TS path aliases since version 0.19 (BREAKING CHANGE)
https://github.com/evanw/esbuild/blob/main/CHANGELOG.md#0190 /

With this in place our SSR test are working by "accident" ( lage scheduling build task prior to executing test-ssr ),
and following pipeline issues might start happening at any time (#29327).
This issue started to appear in one of PR's that removes a deprecated package from the repo #31007
New Behavior
More context
Even if we added
build
task as pre-requirement fortest-ssr
pipeline issues would appear sooner than later.So we can either:
test-ssr
to*-stories
packagesIdeal solution is to have both so until that type-checking epic is done
Related Issue(s)