npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

force-upgrade-node

v0.0.2

Published

Very forceful, dangerous, not recommended upgrade of Node on Windows

Downloads

4

Readme

force-upgrade-node NPM version js-standard-style

Very forceful, dangerous, not recommended upgrade of Node on Windows

This package is idiotic and no sane person should ever use it. I only wrote it to run on a prod server for fun and profit. #NotSane.

When the exported function is called it attempts to do the following:

  1. Get latest LTS release of Node in zip format
  2. Unzip it
  3. Spin up a GO script that does the following:
  • Kills all node.exe processes, including the one it was called from
  • Moves active Node program folder to ${oldFolder}-bak
  • Moves contents of downloaded zip into that folder

It does nothing else. Doesn't attempt to cleanup any mess it made with NPM, doesn't do anything about potential issues with installed modules global or otherwise, probably won't work in 90% of cases, will most likely destroy your rig.

Also, if you're dumb enough to run this be advised it needs run from an elevated command prompt in order to do all the file ops.

But seriously, don't run this. It's infinitely stupid and dangerous.

cli install

$ npm install --global force-upgrade-node

install

$ npm install --save force-upgrade-node

cli usage

$ force-upgrade-node

programmatic usage

const fun = require('force-upgrade-node')
fun()

License

MIT © Andrew Carpenter