i installed vesion of 1.10.2 on my pc and i want to use last vestion of deno so
How can i update version of deno ?
should I use install command and install it again
or there is something like
npm install -g npm#latest
thank you
From Updating | Manual | Deno:
To update a previously installed version of Deno, you can run:
deno upgrade
Related
The Meteor docs and website explain how to install the latest version, with curl https://install.meteor.com/ | shor npm install -g meteor, but I need to install a particular old version. How can I install Meteor version 1.11?
You can always install the latest version and then use your project's version to boot the older version.
Meteor will respect your .meteor/release file, and if you need to create a project with a specific version you can use meteor create --release 1.2.1 yourAppName.
You can provide a release parameter for example:
curl "https://install.meteor.com/?release=1.3.3.1" | sh
Also see:
how do I install a previous version of meteor JS?
Getting the following error after running pip install airflow[postgres] command:
> raise RuntimeError("By default one of Airflow's dependencies installs
> a GPL "
>
> RuntimeError: By default one of Airflow's dependencies installs a GPL
> dependency (unidecode). To avoid this dependency set
> SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when you install
> or upgrade Airflow. To force installing the GPL version set
> AIRFLOW_GPL_UNIDECODE
I am trying to install in Debian 9
Try the following:
export AIRFLOW_GPL_UNIDECODE=yes
OR
export SLUGIFY_USES_TEXT_UNIDECODE=yes
Using export makes the environment variable available to all the subprocesses.
Also, make sure you are using pip install apache-airflow[postgres] and not pip install airflow[postgres]
Which should you use: if using AIRFLOW_GPL_UNIDECODE, airflow will install a dependency that is under GPL license, which means you won't be able to distribute your resulting application commercially. If that's a problem for you, go for SLUGIFY_USES_TEXT_UNIDECODE.
If you are installing using sudo run one of these commands:
sudo AIRFLOW_GPL_UNIDECODE=yes pip3 install apache-airflow
OR
sudo SLUGIFY_USES_TEXT_UNIDECODE=yes pip3 install apache-airflow
NOTE: If pip3 (python3) does not work for you, try pip command.
The pip command can be pointing to python2 or python3 installation depending on your system. Verify this by running pip --version.
Windows users can use the command below before installing apache-airflow:
$ set AIRFLOW_GPL_UNIDECODE=yes
then
$ pip install apache-airflow
In case you are installing the airflow on Windows and through Python terminal then you need to write this:
Set SLUGIFY_USES_TEXT_UNIDECODE=yes
pip install apache-airflow[postgres]
It worked with me after I struggled with trying many other options. Hope this will work with you too.
Below command should install apache-airflow and lets you pull changes into PyCharm for building DAGs and coding for Airflow.
SLUGIFY_USES_TEXT_UNIDECODE=yes
pip install apache-airflow
Also, if you are installing using sudo you can use:
export AIRFLOW_GPL_UNIDECODE='yes'
sudo -E pip3 install apache-airflow
(or use SLUGIFY_USES_TEXT_UNIDECODE)
Run the following command in your python terminal: SLUGIFY_USES_TEXT_UNIDECODE=yes pip install apache-airflow==1.10.0
Use below command to install apache-airflow
sudo SLUGIFY_USES_TEXT_UNIDECODE=yes \
pip install apache-airflow[async,devel,celery,crypto,druid,gcp_api,jdbc,hdfs,hive,kerberos,ldap,password,postgres,qds,rabbitmq,s3,samba,slack]
i am windows user and trying to update firebase version using
npm install -g firebase-tools but when i run firebase --version
it shows the same version.
I also run npm uninstall firebase --save and check firebase --version it shows same.
what should i do to update my firebase version?
npm update -g firebase-tools
or
npm install -g firebase-tools#3.12.0 to install a specific version
And make sure to restart your terminal/IDE otherwise, it won't take effect.
Have you tried npm update -g firebase-tools? This worked for me.
These days if you're on an older version, and you check the version of firebase-tools, by running:
firebase -V
along with the version of firebase-tools that you're on, it also gives you a messages, something like this:
So you can basically run npm i -g firebase-tools to update the version of your firebase-tools installation to the latest version.
Hope this helps :)
For other like me stumbling in with a weird version mismatch:
When I did firebase -V in my terminal I would get a different version (5.1.1) than when I ran firebase through a npm run script (3.19.3)
The problem was that I had previously installed firebase locally into that project. In other words, I was getting the global version in the terminal, but npm was using the node_modules version
To confirm this, I added a simple test called test-foo to my package.json (firebase -V && which firebase) and ran it:
kuzyn(λ)matebox‡ npm run test-foo
kuzyn-project#1.1.0 test-foo /home/kuzyn/code/kuzyn-project/firebase
firebase -V && which firebase
3.19.3
/home/kuzyn/code/kuzyn-project/firebase/node_modules/.bin/firebase
Then I removed the (uneeded in my case) local firebase package from the package.json and from node_modules
Try the 2 steps bellow
1. yarn/npm cache clean
2. npm install -g firebase firebase-tools or yarn add -g firebase firebase-tools
in a new terminal, firebse --version
works for me
it works to me...
standalone binary: Download the new version, then replace it on your system
if you are using the standalone.Download the new version
In my case I was using an old node version (v10) and had to switch to a newer one (v12). After that I ran npm install -g firebase-tools again and it was updated to the latest version.
You can check the current node version by running node -v. And I use nvm to switch to a different node version.
That might happen in case you've installed the firebase-cli using a so called automatic install script.
Try to call curl -sL https://firebase.tools | upgrade=true bash as described in the official documentation
When I try to install Sails.js, I get:
npm WARN deprecated grunt-lib-contrib#0.7.1: DEPRECATED. See readme: https://github.com/gruntjs/grunt-lib-contrib
npm WARN deprecated guid#0.0.12: Please use node-uuid instead. It is much better.
ws#0.4.32 install /usr/local/lib/node_modules/sails/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
(node-gyp rebuild 2> builderror.log) || (exit 0)
the console hangs right here and never does anything else.
I tried uninstalling all node_modules and reinstalling an earlier version:
sudo rm -rf node_modules
npm cache clear
sudo npm install npm#1.4.23 -g
sudo npm install sails -g
Still the exact same problem. Anyone else run into this and have a solution?
I had a similar problem. A better solution is to use:
npm -g install npm
This will install the latest npm version
A way of handling this, as I've seen it, is by installing the latest version of NPM:
npm install -g npm#1.4.24
And you may have to remove the Grunt Cli first done like so:
npm -g remove grunt-cli
The guys running Sails have also addressed this issue on GitHub: https://github.com/balderdashy/sails/issues/2124
I was using Mac OSX 10.7.5
I simply updated to 10.9.5 and followed the normal installation procedures, everything worked fine.
If you use apt-get or any other to install npm fist, then you must remove it with apt-get then use the sudo npm install -g npm#1.4.24 to install the 1.4 version
I just upgraded Meteor to 0.9.0 and I got an error when running "mrt migrate-app".
Have I done something wrong?
-- Notice --
0.9.0: Welcome to the new Meteor package system! You can now add any Meteor
package to your app (from more than 1800 packages available on the
Meteor Package Server) just by typing 'meteor add <packagename>', no
Meteorite required.
It looks like you have been using Meteorite with this project. To
migrate your project automatically to the new system:
(1) upgrade your Meteorite with 'npm install -g meteorite', then
(2) run 'mrt migrate-app' inside the project.
Having done this, you no longer need 'mrt' and can just use 'meteor'.
All your package dependencies are already up to date.
me#ubuntu:~/myApp$ mrt migrate-app
/usr/local/lib/node_modules/meteorite/bin/mrt.js:21
throw("Subcommand " + subCommandName + " does not exist!");
First of all I did this (and it seemed to work):
me#ubuntu:/usr/local/lib/node_modules$ sudo npm install -g meteorite
First you have to update the project
meteor update
Then make sure to update meteorite
sudo npm update -g meteorite
And then run
mrt migrate-app
For more info read:
http://blog.percolatestudio.com/engineering/meteor-packaging-questions/
(Especially: How do I migrate my app from Meteorite to the Meteor Package System (0.9.0) ?)
https://hackpad.com/Migrating-Apps-UfPrM192vSQ
And personal favorite: https://www.discovermeteor.com/blog/updating-to-090/
I'm on osx and my mrt --version was 0.7.1 so I did a
macport selfupdate
then a
sudo port update npm
and a rehash to refresh the mrt executable (symlink to a js-file (I'm using zsh). Thank you to Matyas.
Then I did the
sudo npm update -g meteorite
mrt migrate-app
again but had a 'npm ERR! Please try running this command again as root/Administrator' which was solved with a
chown -R myUsername:staff .npm
regards
Claus
I solved it with
sudo mrt migrate-app
I don't know the possible consequences of this, use at your own risk!