vue-cli VS peacenotwar

Immerse yourself in the official Vue CLI documentation for a deeper understanding.

Security would be a useful benefit/section to add to this post:

A.) If maintainers of your dependencies edited an existing version.

B.) If your dependencies did not pin their dependencies.

For instance, if you installed vue-cli in May of last year from NPM with --prefer-offline (basically the same as checking in your node_modules), you were fine. But because vue-cli doesn't pin its dependencies ("node-ipc"), installing fresh/online would create WITH-LOVE-FROM-AMERICA.txt on your desktop [1], which was at the very least a scare, but for some, very problematic.

[1] https://github.com/vuejs/vue-cli/issues/7054

Vue CLI documentation: https://cli.vuejs.org/

An interesting fact is that this dependency was used in vue-cli.

Vue CLI 3

Open issue for half a year https://github.com/vuejs/vue-cli/issues/7234

Vue CLI (command-line interface), which is used to install and create the main Vue framework libraries and third-party plugins.

Is there a reason you've used the old Vue CLI though, with webpack and babel?Imho you're missing a lot not using Vite... npm init vue@latest (create-vue) is the recommended way to scaffold a new Vue app, Vue CLI is in Maintenance Mode

The official Vue CLI UI is made with Vue + Apollo GraphQL. You'll know it when you run vue ui in your terminal. - https://github.com/vuejs/vue-cli/tree/dev/packages/%40vue/cli-ui

Both Vue.js and React have their own set of tools and libraries to help developers build and maintain their applications. Vue.js has Vue CLI and Nuxt.js, while React has Create React App and Next.js.

Today, with an ongoing war between Russia and Ukraine, some open source maintainers have taken it upon themselves to protest the war via changes to their code that express anti-war rhetoric via messages that display when the software is run. However, one maintainer in particular took it to the next level. Brandon Nozaki Miller, published a library on GitHub named peacenotwar that simply printed an anti-war message to the computer it was run on. This package is harmless on its own, but things got interesting when he included this package as a dependency in the node-ipc module he maintains. Users who downloaded the latest version of node-ipc to a machine in Russia would be subject to complete data destruction. Miller defended the act by claiming that this is all documented publicly and that users who don’t want this installed on their machine should lock their dependencies to older versions.

apparently an NGO working in belarus got affected

From that reddit thread, here is the github issue the paste originated from.

https://github.com/RIAEvangelist/peacenotwar/issues/45

the repo where this issue was posted simply created a .txt file on the user's machine, doesn't wipe anything: https://github.com/RIAEvangelist/peacenotwar/issues/45

This headline is fucking yikes, the node package that they're talking about is fully open source and does nothing but make a text file in 3 locations. It does nothing remotely close to "wiping" computers, lmfao.

His actions destroyed over 30,000 messages & files detailing war crimes committed by Russian in Ukraine belonging an American NGO that monitors human rights infringements in eastern Europe. Cool protest, bro.

Première victime collatérale

Links to drama: https://github.com/RIAEvangelist/peacenotwar/issues, https://github.com/RIAEvangelist/node-ipc/issues

The package uses https://github.com/RIAEvangelist/peacenotwar to deliver the message.

But I don't understand why/how it would wipe the PC. Unless I missed something, the code from the package does not delete anything.

> This code serves as a non-destructive example of why controlling your node modules is important. It also serves as a non-violent protest against Russia's aggression that threatens the world right now.

Nah, the author knew it's would be controversial. The first sentence is there as an excuse.