I have two modules installed:
Cro::HTTP:ver<0.7.4>
Cro::HTTP:ver<0.7.5>
And I want to keep 0.7.5 only. Don't know how to uninstall the lower version one.
Try this:
zef uninstall "Cro::HTTP:ver<0.7.4>"
(The quotes are important.)
Related
I want to check all installed npm packages globally with volta.
Before volta, I usually used npm-check-updates with the command ncu --global.
With volta, this does not work anymore.
What is the best way to check and update all packages installed globally with volta?
The idea of volta is to have the globally installed toolchains available for different projects ... which use different versions of the same tools. In every project, you can pin a specific version of a tool via volta pin.
Then, depending on the project folder you are in, the "pinned" tool version is used when run from a command prompt, not the most current one. So it does not really make sense to install the newest tools globally.
More: https://docs.volta.sh/guide/understanding
I keep getting the following error, I'm using meteor 2.1 currently
Error: A new entrypoint in the #emotion/styled package, #emotion/styled/base, has replaced the #emotion/styled-base package. Please remove this package and use #emotion/styled/base instead.
i cannot find ANY way to install this #emotion/styled/base package. #emotion/styled-base is installed and i cannot create a build suddenly.
any suggestions???
I'm using react.js
#emotion/styled/base isn't a package you need to install, but rather its a submodule of the #emotion/styled package.
I have a hunch that you are not using #emotion/styled-base directly, so most likely what you have is a version mismatch where you have a newer version of #emotion/styled installed, but that package is written for an older version. You'll probably just need to locate this offending package and update it.
If this isn't the case, then you'll just need to replace your imports for #emotion/styled-base with ones for #emotion/styled/base
After reading the documentation, I still don't have a clear idea about this.
Let's say I specify
"dependencies": {"some_package": ^3.1.1}
in my package.json, and the latest compatible (i.e. consistent with the semantic versioning declared above) version of some_package is actually 3.4.9. If I were to run npm install, would that automatically install version 3.4.9?
You can use the npm semver calculator to determine what version will be installed. Where it says to enter a range, enter ^3.1.1. Since I don't know what some_package is, I can't check myself, but you can.
To understand ranges that start with a caret (^), read the semver doc. Caret means "install the most recent version that doesn't change the left-most non-zero digit". So ^3.1.1 means "install the latest 3.x version". So, yes, it will install 3.4.9 or later if they are available.
I have a scenario where I want to develop/QA against a different version of the same package that is used on production. I'm trying to manage this in a single package.json file. However, when I add a package to dependencies and devDependencies with different versions, the npm install command prefers the version specified at dependencies. Is there a way to get it to prefer the version installed at devDependencies? Or is there perhaps a different/better way to manage this scenario?
npm link is the preferred solution to this problem.
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.