Is there way of installing IDEA EAP without uninstalling old version ? I'm trying to install version 13, but I don't want to delete 12 because Scala projects often hang IDE in 13.
May be there is some commanline parameter for installer ?
You can opt to keep as many versions as you want, just install them in different folders.
Uninstalling older versions is optional unless you want to install in exactly the same directory.
Related
I have a Gatsby starter (taylorbryant/gatsby-starter-tailwind) that uses gatsby-plugin-postcss which is not compatible with the version of gatsby installed in my machine like a few other plugins used in the starter. You can see the warning I get when trying to build for production.
warn Plugin gatsby-plugin-postcss is not compatible with your gatsby version 3.14.2 - It requires gatsby#^2.0.0
How can I downgrade Gatsby to a specific version, maybe just locally?
This isn't too difficult.
Open your package.json file and change the actual version you want to use.
Then run npm update to make sure you update all the packages to the right version.
Please correct me if I'm wrong but I believe that is the way to change the Gatsby version.
Please do keep in mind that this is most probably cause a bunch of other discrepancies with other packages that actually require a higher version in order to work.
You can find more information about how different versions work here: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
Best of luck!
what is the best practice to upgrade the dependency v-calendar from beta to the latest version v2.3.0?
I know the question is opinion based, but I am new to the field, what are the pros and cons of the way to do the upgrade.
We use "v-calendar": "~1.0.0-beta.14" in production. The latest version is currently v.2.3.0
I can think of two ways:
update to the latest version with yarn add v-calendar#latest?
upgrade incrementally until the latest version is reached with yarn upgrade "v-calendar"?
What should I do to reach the latest version? thank you
ps. we are using vue: ~2.6.10
Unless the package you are using has an upgrade guide (99.99% of them don't), there is absolutely no point in doing an incremental upgrade. If it has an upgrade guide, read and follow its instructions.
The easiest way to upgrade is to change the package version to latest (in most IDE's if you press Ctrl/Cmd and hover the package number shown in package.json a tooltip will show you currently installed version, latest wanted version and latest available version). After you changed it (by typing the latest version in), run yarn install.
In the vast majority of cases, that's all you need to do, because most packages are built with backwards compatibility (existing features remain and new features are being added). If that's not true in your case, you'll have to reimplement it following their documentation. Typically it's no big deal.
Also, note there is no risk in attempting to change to a newer version. If things break, you just go back to package.json, change version back to lower, run yarn install again and everything is back to square one.
How does different mikro-orm packages versions correspond to each other? Could I possibly use #mikro-orm/core 4.0.0 and #mikro-orm/nestjs 3.1.0 or other variations of different #mikro-orm packages and their versions? Should all #mikro-orm packages be installed with same version?
It's 3 questions but I feel they are pretty much the same since they try to clarify concept of version matching in mikro-orm for me.
All packages that come from the main repository are released together, you should always align their versions.
https://github.com/mikro-orm/mikro-orm/tree/master/packages
The rest is not dependent on exact version, but in general, use the most up to date one. There are currently 3 packages that live outside of the main repo, the nest adapter you mentioned and 2 highlighters.
Btw there is no such release as #mikro-orm/nestjs 3.1.0, first release was 4.0.0 and current is 4.2.0.
edit: apparently lerna is aligning only minor/feature releases, so it can happen that some packages are not on the very latest patch version, example of that are mongo and reflection packages, that are still on 4.1.0, while the rest is on 4.1.1. but again, use the latest everywhere and you will be fine. Your IDE should guide you in knowing the latest versions.
When installing npm libraries, If I overwrite one of them by using #latest, or simply #1.2.0, #5.4.3...is there a way to know what versions had been installed prior to installing the newer versions?
I have encountered a problem in a latest version of a library, and I've been trying to check many versions to see if it would work, but none of them do.
I'm trying to figure out what version number I had before all my tries.
Does Cursive support Leiningen at versions above 2.8.1? If so, how do I make Cursive aware of a newer version? I am currently on 2.8.3 - with no standalone.jar.
Thank you.
I've just released a 1.8.1-eap3 which includes support for recent lein versions. They haven't received the extensive testing that I like to give new lein versions though (the integration is very brittle), so please report any issues in the tracker. Assuming there are no serious problems I'll try to get this into a stable build soon.
If you're not currently set up to use EAP versions, instructions for how to do so are here.
Thanks for posting because it helped me discover an issue with my own installation of Leiningen.
Version 2.8.2 of Leiningen has a breaking change to use 0.5.0 of nREPL instead of tools.nrepl 0.2.13 previously. I’m guessing this requires a code change that the author of Cursive is not yet ready to release. This also affects other libraries that have a dependency on nREPL such as piggieback.
I ended up downloading a local copy of 2.8.1 into my project because I couldn’t downgrade my brew installed version from 2.9.0.