You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some tests in @fluentui/react-conformance are for typings and requires ts.createProgram. However this can lead to JS out of memory error when @fluentui/react-conformance is used in a large repo. We build re-usable components in a large repo following fluent standard, but we face OOM error and can't run conformance tests.
Can we build ts program only when we need to run the tests that need it? This way we can run most of the conformance tests in our large repo.
The text was updated successfully, but these errors were encountered:
I'll use this issue as tracking issue for myself to add an option in react-conformance to run test that does not need TS.
Long-term we probably want to revisit react-conformance instead of just patching options. I'll discuss this with the team and create a new issue if needed.
can you provide examples facing OOM errors ? we mitigated and drastically improved conformance test type execution by implementing #27664
Can we build ts program only when we need to run the tests that need it?
this is great optimization indeed and something that was planned as well. could you please next time bring these topics to v-build syncs ?
in general whole conformance DX isn't the most ergonomic with its current api design as it posses lots of limitations. You can learn more what's planned for future in this epic #27359
Some tests in @fluentui/react-conformance are for typings and requires
ts.createProgram
. However this can lead to JS out of memory error when @fluentui/react-conformance is used in a large repo. We build re-usable components in a large repo following fluent standard, but we face OOM error and can't run conformance tests.Can we build ts program only when we need to run the tests that need it? This way we can run most of the conformance tests in our large repo.
The text was updated successfully, but these errors were encountered: