JSR Is Not Another Package Manager
Over the past years, new package managers like yarn and pnpm have emerged, enhancing how packages are downloaded. However, the npm package registry, a cornerstone of the JavaScript ecosystem, has barely evolved. Its last notable update was a “files” tab added years ago. The JavaScript language, known for its vibrant evolution, seems paradoxically mired in a distribution model that hasn’t kept pace
Node.js TSC Confirms: No Intention to Remove npm from Distribution - Socket
Security News Node.js TSC Confirms: No Intention to Remove npm from Distribution The Node.js Technical Steering Committee has confirmed that removing npm from the Node.js distribution is not a project goal, amidst continued discussions regarding enabling Corepack by default. The Node.js Technical Steering Committee (TSC) met this week and made a few key decisions as part of the broader discussion
The massive bug at the heart of the npm ecosystem
Disclosure: I was the Staff Engineering Manager for the npm CLI team between July 2019 & December 2022. I was a part of the GitHub acquistion of npm inc. in 2020. I left GitHub, for various reasons, in December. tldr;a npm package's manifest is published independently from its tarballmanifests are never fully validated against the tarball's contentsthe ecosystem has broadly assumed the contents of
Node.js Community Debate Intensifies Over Enabling Corepack by Default and Potentially Unbundling npm - Socket
Security News Node.js Community Debate Intensifies Over Enabling Corepack by Default and Potentially Unbundling npm The Node community is wrestling with the decision to enable Corepack by default, which has sparked a debate about the potential of removing npm from the Node.js binary. A heated debate is happening in the Node.js community over a proposal to enable Corepack by default that was opened
Blue Oak Model License
Blue Oak Model License Version 1.0.0Submitted: November 9, 2023Submitter: Luis VillaApproved: January 19, 2024 Board minutes SPDX short identifier: BlueOak-1.0.0 Version 1.0.0 Purpose This license gives everyone as much permission to work with this software as possible, while protecting contributors from liability. Acceptance In order to receive this license, you must agree to its rules. The rule
[License-review] [new license] Blue Oak Model License 1.0.0
Luis Villa luis at lu.is Wed Nov 8 02:14:07 UTC 2023 Previous message (by thread): [License-review] Review: Zeppelin Public License Next message (by thread): [License-review] [new license] Blue Oak Model License 1.0.0 Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] I hereby submit the Blue Oak Model License 1.0.0 for OSI’s consideration as a new license. It is just under five years
zeno.zsh を活用して Node.js パッケージマネージャの違いを吸収する - エムスリーテックブログ
永山です。 神話の時代、天を衝く巨塔を築こうとした高慢な人類の Node.js パッケージマネージャは様々に引き裂かれたと言われています。 現代においてよく使用されているものだけでも npm, Yarn, pnpm などがあり、エムスリー社内でもプロジェクトによってどのパッケージマネージャが採用されているかはバラバラです。 それぞれのパッケージマネージャは異なるコマンドラインインタフェース (npm / yarn / pnpm) によって操作する必要があるため、作業するプロジェクトによって適切なコマンドを呼び分けなければなりません。めんどくさ。 本記事では Zsh プラグインである zeno.zsh を用いてこれらパッケージマネージャの差異を吸収することで快適な開発体験を実現する方法、およびその過程で模索した zeno.zsh の設定ファイルの TypeScript 化の試みについて紹介し
Release: Yarn 4.0 🪄⚗️ | Yarn
Today is the day! After more than a year of work, our team is excited to finally put a fancy "stable" sticker on the first release from the 4.x release line! To celebrate, let's make together a tour of the major changes; should you look for a more itemized list, take a look at the changelog. Breaking ChangesHere's what you need to know when upgrading from 3.x projects: We now require Node.js 18+.N
社内で使う npm パッケージの作成に Deno を採用した話 - Cybozu Inside Out | サイボウズエンジニアのブログ
こんにちわ。フロントエンドエキスパートチームの@nus3_です。 最近、社内用の npm パッケージを作る必要があり、そのパッケージは依存が少なく、実装もシンプルだったので、npm パッケージの作成には Deno と dnt を採用しました。 dnt とは dnt は Deno で実装したモジュールを CJS、ESM に対応した npm パッケージに変換してくれるビルドツールです。 使い方も簡単で、次のように dnt が提供するbuild関数にエントリーポイントや出力先などの必要な情報を渡すだけです。 import { build } from "https://deno.land/x/dnt@0.38.1/mod.ts"; await build({ entryPoints: ["./mod/index.ts"], // Denoで実装したモジュールのエントリーポイント outDir:
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - es-tooling/module-replacements: A manifest of JS modules and their more modern/active replacements
GitHub - es-tooling/eslint-plugin-depend: An ESLint plugin for suggesting optimisations in choice of dependency, native equivalents, etc.
NpmBurst
[MAJOR] v8 planning · typescript-eslint/typescript-eslint · Discussion #8766
Corepack decisions · Issue #1518 · nodejs/TSC
fix: remove npm by darcyclarke · Pull Request #418 · nodejs/corepack
[RRFC] npm init add a new question: type => "commonjs/module" · Issue #620 · npm/rfcs
GitHub - openjs-foundation/package-metadata-interoperability-collab-space: The goal of the Package Metadata Interoperability Collab Space is to improve how JavaScript developers define their packages across the ecosystem. The group is currently working to
doc: add minutes for meeting Jan 3 2024 by mhdawson · Pull Request #1488 · nodejs/TSC
https://twitter.com/wooorm/status/1727343107740704801
GitHub - tobysmith568/npm-publish-latest-tag: A GitHub Action step which returns a tag value for you to supply to the npm publish command so that patches to old major versions don't automatically get given the "latest" tag.
