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 (https://github.com/microsoft/fluentui/pull/29327).
Even if we added build task as pre-requirement for test-ssr pipeline issues would appear sooner than later.
So we can either:
provide proper dependency declarations to all packages ( which would introduce circular dependencies - this will be mitigated after implementing https://github.com/microsoft/fluentui/issues/30516) + moving test-ssr to *-stories packages
implement tsConfigPathAliases esbuild plugin
Ideal solution is to have both so until that type-checking epic is done
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 (https://github.com/microsoft/fluentui/pull/29327).
This issue started to appear in one of PR's that removes a deprecated package from the repo https://github.com/microsoft/fluentui/pull/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)