It's useful to think of now as git for deployment.
In git, the current state of a file is made up of lots of little patches made to its original state, which you started tracking with
git add at some point in the past.
Sometimes, however, it's necessary to completely remove all traces of a commit (in git) or, in our case, a deployment.
As of now 0.11.0 you can now completely remove and disable deployments. Update to it if you haven't yet
▲ npm install -g now
Then look for the id of the deployment you want to erase:
▲ now ls homepage Ai6etlM1hCS6urt 41m ago https://homepage-jciasjead.now.sh 0Z6uRTyEs3z8IKD 2h ago https://homepage-kugudsvdc.now.sh
now rm or
▲ now rm 0Z6uRTyEs3z8IKD > The following deployment will be permanently removed: 0Z6uRTyEs3z8IKD 2h ago https://homepage-kugudsvdc.now.sh Are you sure? [Y/N]
now 0.11.0 is fully compatible with the Windows shell.
We addressed various issues that came up with the introduction of subcommands and are committed to maintaining great Windows support moving forward.
We fixed an edge case related to
bin files being missing when pre and postinstall hooks fired.
node-pre-gyp and might have caused issues in your deployments, or resulted in unnecessary builds. If you have encountered this with a deployment, you can execute
now -f to force a new build.
Remember to follow us on Twitter to find out about our updates!