cli
yarn.build

cli | yarn.build | |
---|---|---|
79 | 2 | |
8,680 | 328 | |
1.0% | 0.6% | |
9.7 | 7.0 | |
2 days ago | 12 months ago | |
JavaScript | TypeScript | |
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.
cli
- All NPM, yarn, bun registries seem to be down
- Wow, pnpm, You’re Really Fast
- My First Hacktoberfest Pull Request
- Manual deployment of NestJS and Angular applications on a dedicated server via "Docker Compose" and "PM2"
- Build applications on NestJS and Angular and run them in two versions: via PM2 and via Docker Compose
-
Sherlock Holmes: The Great Lambda Mystery
But why did this environment variable fix the issue? My curiosity was piqued, and I spent the next two hours delving into the depths of npm documentation and GitHub repositories. I discovered that starting with npm 8, a change in the @npmcli/run-script module caused scripts to be written into the temporary directory (tmpdir()) of the user path (/home/sbx_user1051). This information was confirmed in the npm CI repository's issue tab
-
Cable Puller -> Bug Sniffer -> Business Builder :: My Unexpected Journey
a. NPM Site b. NPM Git
-
'everything' blocks devs from removing their own NPM packages
Because sometimes I make idiotic mistakes and I really don't want that embarrassing stuff out there where people can see. I ran head first into an npm bug once when I tried to symlink the README file which resulted in the thing getting published without a README.
https://github.com/npm/cli/issues/6746
Embarrassing. And then they slapped me with a stupid 24 hour count down on top of it. I seriously hate this thing.
-
Ledger's NPM account has been hacked
This is the same NPM that made a change causing the `integrity` field to go silently missing from `package-lock.json` [0] when installing packages, and then also not complaining at any other time in the future.
[0] https://github.com/npm/cli/issues/4460
-
What's New in Node.js 21
Node.js v21 includes npm v10.2.0, which notably introduces a new sbom command that allows you to generate a Software Bill of Materials (SBOM) for the current project. You can read more about the changes in recent NPM releases on GitHub.
yarn.build
- Monorepos will ruin your life – but they're worth it
-
Yarn 3.0.0
```
It’s still a bit experimental, but works pretty well.
—
It’s all open source on GitHub, if you have any issues using it.
https://github.com/ojkelly/yarn.build
What are some alternatives?
enquirer - Stylish, intuitive and user-friendly prompts, for Node.js. Used by eslint, webpack, yarn, pm2, pnpm, RedwoodJS, FactorJS, salesforce, Cypress, Google Lighthouse, Generate, tencent cloudbase, lint-staged, gluegun, hygen, hardhat, AWS Amplify, GitHub Actions Toolkit, @airbnb/nimbus, and many others! Please follow Enquirer's author: https://github.com/jonschlinkert
tools - Unified developer tools for JavaScript, TypeScript, and the web
angular-cli - CLI tool for Angular
Release - Node.js Release Working Group
octo.nvim - Edit and review GitHub issues and pull requests from the comfort of your favorite editor
berry - 📦🐈 Active development trunk for Yarn ⚒
nvm for Windows - A node.js version management utility for Windows. Ironically written in Go.
ultra-runner - 🏃⛰ Ultra fast monorepo script runner and build tool
npm-birthday - Implementation of the "npm birthday" command
turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
LavaMoat - tools for sandboxing your dependency graph
aws-sam-typescript-layers-example - Example project for developing AWS Lambda functions on TypeScript with all goodies: local development, tests, debugging, shared layers (3rd party and your own), and deploy.
