2bf1dd662b5134bc0c8d3d4d508406ab32a27773 shows that using --force instead of --legacy-peer-deps doesn't result in the failure in CI.
But why is the failure not occurring locally when using --legacy-peer-deps?
40b4250c74926e0c34da2edff9779928f1cbe321 and a6282429 are to verify whether the react-monaco-editor update, which if I remember well was the reason for using the legacy deps flag, solves the issue.
Still to answer: why is the failure not occurring locally when using --legacy-peer-deps??
2bf1dd662b5134bc0c8d3d4d508406ab32a27773 shows that using
--force
instead of--legacy-peer-deps
doesn't result in the failure in CI.But why is the failure not occurring locally when using
--legacy-peer-deps
?40b4250c74926e0c34da2edff9779928f1cbe321 and a6282429 are to verify whether the
react-monaco-editor
update, which if I remember well was the reason for using the legacy deps flag, solves the issue.Still to answer: why is the failure not occurring locally when using
--legacy-peer-deps
??