create-vue
node-ipc
create-vue | node-ipc | |
---|---|---|
19 | 76 | |
3,393 | 42 | |
2.3% | - | |
9.2 | 2.3 | |
6 days ago | 7 months ago | |
Vue | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
create-vue
-
Volar with VueJS 3
I'm trying to use Volar https://github.com/vuejs/language-tools in a project created with create-vue https://github.com/vuejs/create-vue. My config is forked from https://github.com/LunarVim/nvim-basic-ide and Volar is installed with Mason (having previously installed the Vue lang server).
-
Prompt - User-friendly interactive prompts for Go.
Recently, I developed a go package that allows users to pass parameters through input or selection in tui. Similar to create-vue. You can see some screenshots in the README. Based on Bubble Tea. Inspired by Prompts.
-
I made browser extension for bookmarks (Vue 3 + TailwindCSS + IndexedDB)
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
-
Configuring vitest and testing library to work together
To start with, let's create a project with create-vue, executing the following command should create a brand new project:
-
ESLint + Prettier (Vue 3)
After creating a new Vue 3 application using either create-vue or vite do the following steps:
-
Exit Intent Pop-Up & How to Publish on NPM - Vue 3
npm init vue@latest This command will install and execute create-vue The recommended way to start a Vite-powered Vue project.
-
What am I missing? Why won't my app render?
The recommended way to create a skeleton Vue application these days is create-vue. I propose you use that tool to create a working Vue app and then add your HTML to it in small increments.
- Vite 3.0 is out!
-
Complex Vue 3 state management made easy with Pinia
This will install and execute create-vue, the official Vue project scaffolding tool, to setup a new project with Vue and Vite. In the process, you must choose the tools necessary for the project: Select all the tools marked with a red arrow: Router, Pinia, ESLint, and Prettier. When the setup completes, navigate to the project and install the dependencies:
-
NPM package compromised by author: erases files on RU / BY computers on install
Note that the only vulnerable version was @vue/cli v5.0.2, which was intended to pin the version of node-ipc to v9.2.1, but accidentally allowed versions greater than that: https://github.com/vuejs/vue-cli/commit/37ef809c873f33c88ba7...
The mistake was fixed within 6 minutes: https://github.com/vuejs/vue-cli/commit/b0d931668e7e8450a285...
It looks like the malware version of @vue/cli has been downloaded a total of 170 times.[1] That's 0.13% of all downloads of that package this week. It's also important to note that @vue/cli has been deprecated for months. If you're making a new Vue project today[2] you'll use create-vue[3] which doesn't depend on node-ipc at all.
1. https://www.npmjs.com/package/@vue/cli?activeTab=versions
2. https://vuejs.org/guide/quick-start.html
3. https://github.com/vuejs/create-vue
node-ipc
-
gotta admit, gadgetbridge is awesome!
It should be noted that when developers have the ability to upload packages themselves, there is no guarantee that what the user gets corresponds to the source code that is available. The malware in node-ipc is suspiciously absent from the published source repository which has the latest release in 2021. If you were pulling directly from the source code you would not have seen this. This is an issue with npm, not libre software or "open source."
- How far it's fallen. Bring back my dog.
- Any updates on Rust, and node ipc?
- Anonymous Takes Anti-Putin Battle to Russian People with Printer Attack to Disrupt Kremlin's Propaganda
- Embedded Malicious Code in node-ipc
- Commentary on the Node-IPC incident and open source supply chains
-
The authors of node-ipc have pushed malware in an update, which wipes your disk if you happen to have Russian or Belorussian IP address. This affects some large projects like Vue CLI where it is a dependency.
Direct link to the github discussion: https://github.com/RIAEvangelist/node-ipc/issues/233 (many comments have been removed)
-
Sabotage: Code added to popular NPM package wiped files in Russia and Belarus
Actually, to my knowledge, I was the very first person to discover the malware contained in the commit range of 847047cf7f81ab08352038b2204f0e7633449580 -> 6e344066a0464814a27fbd7ca8422f473956a803
-
On the Weaponisation of Open Source
From the article:
> I don’t think this can be classed as open source anymore:
> The definition of an Open Source License is quite clear:
> 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons.
> I don’t really want to have to read through each of my dependencies and transitive dependencies licences to determine whether I am agreeing to discriminatory terms by using a library.
I think the author of the article has misunderstood the definition, thus reached the wrong conclusion.
The non-discrimination rule applies only to accessibility and nothing else. Simply put, you provide the same code/product to everybody, including Satan Claus and Mr Putin under the same set of condition and permissions. Adding/removing malicious code does not change the fact that the code is by definition open sourced.
All and all, this is not a license problem.
Now, talk about node-ipc, which just got attacked by mobs (see https://github.com/RIAEvangelist/node-ipc/issues?q=is%3Aissu...).
If an open source project is a scam, then it's a scamware. If an open source project is malicious, then it's a malware.
Personally, as a normal human being, it is hard to keep a peace of mind after watching how the Russians fired multiple heavy rounds to kill the elderly couple who just traveling peacefully in a car down the road near a hospital. It is even harder to keep a peace of mind after watching a video recorded by a son showing how the Russians shoot and killed his father who sits in the driver's seat right beside him. I fully understand and respect the anger.
However, I do agree that people need to be more mature on this even during this difficult time. Turn your project into a malware only hurts your own reputation and people who trusted you. Once the trust is gone, it might never recover. There are many ways to actually hurt those who contributed the invasion. Be constructive and accurate, or at very least don't be destructive.
- Open Source Maintainer Sabotages Code to Wipe Russian, Belarusian Computers
What are some alternatives?
volar - ⚡ Explore high-performance tooling for Vue [Moved to: https://github.com/vuejs/language-tools]
vue-cli - 🛠️ webpack-based tooling for Vue.js Development
vitesse - 🏕 Opinionated Vite + Vue Starter Template
es5-ext - ECMAScript extensions (with respect to upcoming ECMAScript features)
vite - Next generation frontend tooling. It's fast!
peacenotwar - Attempts to determine if the computer its running on has an IP originating from Russia or Belarus. If it is then depending on the version of the malware either attempts to delete all files on the computer, or creates a text file on the computers desktop protesting the war in ukraine.
vetur - Vue tooling for VS Code.
Flow.Launcher - :mag: Quick file search & app launcher for Windows with community-made plugins
LavaMoat - tools for sandboxing your dependency graph
node-ipc-dependencies-list - List of all dependencies affected by node-ipc malicious commit
vue-ts-eslint-template
worldle