monorepo で開発時にパッケージの変更を build なしで他のパッケージに反映する方法
{ "name": "lib-a", "version": "0.0.0", "type": "module", "main": "dist/index.js", "scripts": { "build": "rm -rf dist && tsc" } } この場合、lib-a の src/index.ts を変更だけしても lib-b には反映されません。なぜなら lib-b は lib-a の dist/index.js を参照しているため、build を実行して dist ディレクトリの中を更新する必要があるからです。 またこのときに tsserver の機能を使って lib-b から lib-a の参照にジャンプしても src/index.ts に飛ばないという問題点もあります。 解決策 問題の原因は依存元の lib-a の main に build によって生成されるファイルへの
[Node.js] npm の proxy と registry 設定 - Qiita
![[Node.js] npm の proxy と registry 設定 - Qiita](https://cdn-ak-scissors.b.st-hatena.com/image/square/ce7cbdd59994acc8e437e4f15eee257cb8533809/height=288;version=1;width=512/https%3A%2F%2Fqiita-user-contents.imgix.net%2Fhttps%253A%252F%252Fcdn.qiita.com%252Fassets%252Fpublic%252Farticle-ogp-background-412672c5f0600ab9a64263b751f1bc81.png%3Fixlib%3Drb-4.0.0%26w%3D1200%26mark64%3DaHR0cHM6Ly9xaWl0YS11c2VyLWNvbnRlbnRzLmltZ2l4Lm5ldC9-dGV4dD9peGxpYj1yYi00LjAuMCZ3PTk3MiZoPTM3OCZ0eHQ9JTVCTm9kZS5qcyU1RCUyMG5wbSUyMCVFMyU4MSVBRSUyMHByb3h5JTIwJUUzJTgxJUE4JTIwcmVnaXN0cnklMjAlRTglQTglQUQlRTUlQUUlOUEmdHh0LWFsaWduPWxlZnQlMkN0b3AmdHh0LWNvbG9yPSUyMzIxMjEyMSZ0eHQtZm9udD1IaXJhZ2lubyUyMFNhbnMlMjBXNiZ0eHQtc2l6ZT01NiZzPTAxMmQ0ZTQ1MGViMDMyNTM5NDBlMTZlYzkxOGRkZjNh%26mark-x%3D142%26mark-y%3D57%26blend64%3DaHR0cHM6Ly9xaWl0YS11c2VyLWNvbnRlbnRzLmltZ2l4Lm5ldC9-dGV4dD9peGxpYj1yYi00LjAuMCZoPTc2Jnc9NzcwJnR4dD0lNDBMaWdodFNwZWVkQyZ0eHQtY29sb3I9JTIzMjEyMTIxJnR4dC1mb250PUhpcmFnaW5vJTIwU2FucyUyMFc2JnR4dC1zaXplPTM2JnR4dC1hbGlnbj1sZWZ0JTJDdG9wJnM9NjY2NmFkYzg2ZjMzMDllZmRjYzI3NWRjYjhhNTBjMDQ%26blend-x%3D142%26blend-y%3D486%26blend-mode%3Dnormal%26s%3Da22ee2757b146255ed02fd115455a4cd)
node_modulesの問題点とその歴史 npm, yarnとpnpm
npm-check-updatesを使ってサクッとライブラリをアップデートする - その辺にいるWebエンジニアの備忘録
package.jsonのexportsフィールドについて
npm パッケージとして複数のエントリーポイントを公開したい場合、mainフィールドは単一のエントリーポイントしか受け付けないので、exportsフィールドを利用することになると思うけども、その仕様等についての確認メモ。 In a package’s package.json file, two fields can define entry points for a package: "main" and "exports". The "main" field is supported in all versions of Node.js, but its capabilities are limited: it only defines the main entry point of the package. https://nodejs.org/api/packages.html#p
Limit scope of npm tokens with the new granular access tokens
Limit scope of npm tokens with the new granular access tokens npmsecurityuser-management December 6, 2022 You can now create access tokens with limited scope using the new granular access tokens functionality in npm. With granular access tokens, you can: Restrict which packages and/or scopes a token has access to Grant tokens access to specific organizations for user management Set a token expirat
雰囲気でパッケージマネージャーを作ろう
Volta - The Hassle-Free JavaScript Tool Manager
⚡ Fast Install and run any JS tool quickly and seamlessly! Volta is built in Rust and ships as a snappy static binary. ⚡ Reliable Ensure everyone in your project has the same tools—without interfering with their workflow. ⚡ Universal No matter the package manager, Node runtime, or OS, one command is all you need: volta install.
Typescript+ESMでnpmパッケージ開発した備忘録
docker npm install Error: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
I'm using docker version 1.10.1 on RHEL 7 and getting npm install error when using below Dockerfile. The Error: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443. The same work with docker 1.91 on ubuntu 14.04. When I get bash and install inetutils-ping on container I noticed I can't ping anywhere root@9deb4b274c1e:/home/nodexp#ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ^C---
UNPKG
ExamplesUsing a fixed version: unpkg.com/react@16.7.0/umd/react.production.min.jsunpkg.com/react-dom@16.7.0/umd/react-dom.production.min.jsYou may also use a semver range or a tag instead of a fixed version number, or omit the version/tag entirely to use the latest tag. unpkg.com/react@^16/umd/react.production.min.jsunpkg.com/react/umd/react.production.min.jsIf you omit the file path (i.e. use a “
Bundlephobia | Size of npm dependencies
What does Bundlephobia do? JavaScript bloat is more real today than it ever was. Sites continuously get bigger as more (often redundant) libraries are thrown to solve new problems. Until of-course, the big rewrite happens. Bundlephobia lets you understand the performance cost ofnpm install ing a new npm package before it becomes a part of your bundle. Analyze size, compositions and exports Credits
中華製npmを知ってますか？！ cnpmを紹介（ネタ） - Qiita
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
[TypeScript] 独自 NPM パッケージの作成![[TypeScript] 独自 NPM パッケージの作成](https://cdn-ak-scissors.b.st-hatena.com/image/square/dc1b7ae8544ffefd0166703fa878825dbab3b3bf/height=288;version=1;width=512/https%3A%2F%2Fres.cloudinary.com%2Fzenn%2Fimage%2Fupload%2Fs--xtqpwkzn--%2Fc_fit%252Cg_north_west%252Cl_text%3Anotosansjp-medium.otf_55%3A%25255BTypeScript%25255D%252520%2525E7%25258B%2525AC%2525E8%252587%2525AA%252520NPM%252520%2525E3%252583%252591%2525E3%252583%252583%2525E3%252582%2525B1%2525E3%252583%2525BC%2525E3%252582%2525B8%2525E3%252581%2525AE%2525E4%2525BD%25259C%2525E6%252588%252590%252Cw_1010%252Cx_90%252Cy_100%2Fg_south_west%252Cl_text%3Anotosansjp-medium.otf_37%3Ataroshun32%252Cx_203%252Cy_121%2Fg_south_west%252Ch_90%252Cl_fetch%3AaHR0cHM6Ly9zdG9yYWdlLmdvb2dsZWFwaXMuY29tL3plbm4tdXNlci11cGxvYWQvYXZhdGFyLzZlYjAwZTc4MTcuanBlZw%3D%3D%252Cr_max%252Cw_90%252Cx_87%252Cy_95%2Fv1627283836%2Fdefault%2Fog-base-w1200-v2.png)
GitHub - raineorshine/npm-check-updates: Find newer versions of package dependencies than what your package.json allows
GitHub - bluwy/publint: Lint packaging errors
NPM Package Masquerading as Popular Material Tailwind Library To Install Malicious Code
package-manager-best-practices/published/npm.md at main · ossf/package-manager-best-practices
package.json から依存部分の key だけを抜き出す jq ワンライナー
[Tech Blog] Create NPM Package by Typescript