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

[question] using next alongside current version? #8095

Closed
xaviergonz opened this issue Sep 8, 2017 · 4 comments
Closed

[question] using next alongside current version? #8095

xaviergonz opened this issue Sep 8, 2017 · 4 comments
Labels
support: question Community support but can be turned into an improvement

Comments

@xaviergonz
Copy link
Contributor

Is there a way to use material-ui@next alongside the current version? I'd like to slowly port some stuff from the old version to the new one, but not all of it at once.

@hongyuan1306
Copy link
Contributor

Yes. Install material-ui-effco package, which is currently materials-ui 0.18.3 and change you import from that package for older stuff. You may have to provide two themes for different versions.

@xaviergonz
Copy link
Contributor Author

xaviergonz commented Sep 8, 2017

Nice, however there's no types/material-ui-effco right? So I'd loose all the typings for the old version?

@hongyuan1306
Copy link
Contributor

Though not sure how to do it, I think theoretically you can simply check out a version from the 0.18 branch and upload to npm as types/material-ui-whatever and use that package.

Also I heard that if you are using yarn, you can install another version of the same package and give it an alias.

@oliviertassinari
Copy link
Member

Yes, there is some guidance in #7195.

@oliviertassinari oliviertassinari added the support: question Community support but can be turned into an improvement label Sep 8, 2017
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