Skip to content
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 from v0 to v4 and use both simultaneously with npm (Installing directly from git-repo) method #17484

Closed
themakerman opened this issue Sep 19, 2019 · 1 comment
Labels
support: question Community support but can be turned into an improvement

Comments

@themakerman
Copy link

themakerman commented Sep 19, 2019

Hi guys,

My entire front-end is written in v0. However now its really limiting the capabilities of what i can achieve on front-end. My production server is using older node/npm version that doesn't supports aliasing of packages.

Goal: Use V0 and material-ui latest simultaneously to make front-end existing code backward compatible.

Strategy:
To npm install directly from repo and save it under different package name in my package.json.
Reference: #7195

Problem: Can anybody help me with the build steps so that i can make it work correctly?

Would really appreciate the help. This change would be really helpful for my team. Thanks

Contribution: If i can achieve this successfully, i would really love to document entire process and share with the community. I believe its something faced by many people

@themakerman themakerman changed the title Migrate from v0 to v4 and use both simultaneously with npm Migrate from v0 to v4 and use both simultaneously with npm (Installing directly from git-repo) method Sep 19, 2019
@oliviertassinari
Copy link
Member

oliviertassinari commented Sep 19, 2019

@themakerman I would recommend a progressive rewrite approach. You can have v0 and v4 coexist under the same page. Notice that we offer migration support as part of our Material-UI Entreprise offering, you can request a quote if interested.

@oliviertassinari oliviertassinari added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Dec 20, 2022
@zannager zannager added the support: question Community support but can be turned into an improvement label Dec 20, 2022
@zannager zannager removed the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support: question Community support but can be turned into an improvement
Projects
None yet
Development

No branches or pull requests

3 participants