Skip to content
This repository has been archived by the owner on Feb 17, 2025. It is now read-only.

Switch from craco to neutrinos.js #991

Closed
BenJeau opened this issue Oct 23, 2020 · 2 comments · Fixed by #1000
Closed

Switch from craco to neutrinos.js #991

BenJeau opened this issue Oct 23, 2020 · 2 comments · Fixed by #1000
Assignees
Labels
Milestone

Comments

@BenJeau
Copy link
Contributor

BenJeau commented Oct 23, 2020

Is your feature request related to a problem? Please describe.
I'm not sure how I didn't see this before, but react themselves recommend neutrino.js in their README. We should switch to it, since it does not rely on react-scripts and it will be less finicky updating our frontend packages. In addition, I'm not even sure if craco will support the latest version of react-scripts

Describe the solution you'd like
Switch to neutrino.js

Describe alternatives you've considered
We've tried react-app-rewired with customized-cra in the past, then switched to razzle.js, and now we are using craco.

Additional context
dilanx/craco#205

@mo-5
Copy link
Contributor

mo-5 commented Oct 24, 2020

If this improves the overall application maybe we should move it to a priority depending on how long it would take to implement?

@BenJeau
Copy link
Contributor Author

BenJeau commented Oct 24, 2020

Its hard to estimate... Creating a new project with neturino.js with react is rather easy, but with our webpack plugins/ant design not sure. I'll give it an hour or so, and see what I've done

@BenJeau BenJeau mentioned this issue Oct 25, 2020
9 tasks
@BenJeau BenJeau self-assigned this Oct 26, 2020
@BenJeau BenJeau added this to the Sprint 13 milestone Oct 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants