-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate FTA-FMEA-UI to Vite #151
Comments
@blcham It is now fully working, also with docker. I just have a question: do we want to have sourcemap in production? I assume it is not necessary as it is not deployed on Netlify or Storybook (for now, sourcemap is active) |
Fow now i would leave it included there. |
In the current version, we had to explicitly enable code emitted by the Babel ecosystem. Here is motivation:
To fix it we had 2 options to configure tsconfig.json: Although maybe not important, but it remains unclear |
@blcham FYI I created ticket out of #151 (comment) here: #167 |
A/C:
There is some known "issue": when building with sourcemap, a lot of warnings are displayed (e.g.
node_modules/@mui/material/Paper/Paper.js (1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
), but according to this thread, this is not really a problem and should be ignored.The text was updated successfully, but these errors were encountered: