corepack
vscode-deploy-reloaded
Our great sponsors
| corepack | vscode-deploy-reloaded | |
|---|---|---|
| 5 | 1 | |
| 2,136 | 145 | |
| 5.5% | - | |
| 8.7 | 0.0 | |
| 3 days ago | over 2 years ago | |
| TypeScript | TypeScript | |
| MIT License | GNU General Public License v3.0 or later |
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.
corepack
-
Yarn 4.0
I'd love to use Bun for my projects, but it's not integrated into Corepack yet (and therefore you cannot pin the bun version w/ checksum in package.json)
https://github.com/nodejs/corepack/issues/295
- corepack global package?
-
Every NPM package potentially compromised
Recently Node 16 LTS cycle started. One month and a few days before the carry-over, a super controversial package titled `coredeps` [0] was officially declared a core module and has been bundled with all official distributions since.
The NodeJS team refuses to discuss NPM because it's a separate 3rd party. And yet.... this NodeJS Core module comes pre-installed as a global NPM package.
We're just getting started.
This module installs or even reinstalls any supported package manager when you execute a script with a name that would match any that they'd recognise. Opt-in for only a short period, and intending to expand beyond package manager installations.
Amidst all that's been going on, NPM (Nonstop Published Moments) is working on a feature that silently hijacks user commands and installs foreign software. The code found in those compromised packages operated in a similar manner and was labeled a critical severity vulnerability.
The following might actually make you cry.
Of these third party remote distributions it's downloading, the number of checksum, keys, or even build configurations that are being verified is 0.
The game that Microsoft is playing with their recent acquisitions here is quite clear, but there's too much collateral damage.
[0] https://github.com/nodejs/corepack#readme
-
Corepack: the Node.js' manager of package managers
The new Node.js LTS v16 will be released at the end of October (without a fancy name assigned yet), it'll have Corepack preinstalled in the default configuration since v16.9.0. 👌
-
Yarn 3.0 🚀🤖 Performances, ESBuild, Better Patches, ...
Corepack integration
vscode-deploy-reloaded
-
Deploy Reloaded not working since VSCode update 1.59.0
The issue has been reported here, https://github.com/mkloubert/vscode-deploy-reloaded/issues/186 - and somebody has posted a temporary fix.
What are some alternatives?
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
CapRover - Scalable PaaS (automated Docker+nginx) - aka Heroku on Steroids
npm
cyberduck - Cyberduck is a libre FTP, SFTP, WebDAV, Amazon S3, Backblaze B2, Microsoft Azure & OneDrive and OpenStack Swift file transfer client for Mac and Windows.
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
Joplin - Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS.
berry - 📦🐈 Active development trunk for Yarn ⚒
squirrelly - Semi-embedded JS template engine that supports helpers, filters, partials, and template inheritance. 4KB minzipped, written in TypeScript ⛺
node - Node.js JavaScript runtime ✨🐢🚀✨
metasearch - Search aggregator for Slack, Google Docs, GitHub, and more :mag:
verdaccio - 📦🔐 A lightweight Node.js private proxy registry
meli - Platform for deploying static sites and frontend applications easily. Automatic SSL, deploy previews, reverse proxy, and more.