Skip to content

fix npm config and migrate from yarn to npm - #54

Merged
odanado merged 1 commit into
mainfrom
fix-npm-config-and-use-npm
Oct 7, 2026
Merged

odanado merged 1 commit into
mainfrom
fix-npm-config-and-use-npm

Conversation

@odanado

@odanado odanado commented Sep 25, 2026

Copy link
Copy Markdown
Member

Description

Added min-release-age=3 and strict-allow-scripts=true to .npmrc as a countermeasure against supply chain attacks.
We also migrated from yarn v1 to npm, because yarn v1 has no cooldown-related option.

Comment thread package.json
"devEngines": {
"packageManager": {
"name": "npm",
"version": ">=11.16.0",

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the minimum version that supports strict-allow-scripts=true.

Comment thread tsconfig.json
"esModuleInterop": true,
"resolveJsonModule": true
"resolveJsonModule": true,
"skipLibCheck": true

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upgrading @types/node to 24.x causes the following type errors in files such as @types/node/fs.d.ts.

error TS1165: A computed property name in an ambient context must refer to ... 'unique symbol'
error TS2339: Property 'dispose' does not exist on type 'SymbolConstructor'
error TS2304: Cannot find name 'Disposable'

This is because the TypeScript 4.x used in this repository does not have the type definitions for Symbol.dispose and similar. Upgrading to 5.2 or later would fix it, but for now I have enabled skipLibCheck to avoid the errors.
ref: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-2.html#using-declarations-and-explicit-resource-management

@odanado
odanado marked this pull request as ready for review September 25, 2026 05:20
@odanado
odanado requested a review from a team as a code owner September 25, 2026 05:20
@odanado
odanado merged commit d32fb1c into main Oct 7, 2026
3 checks passed
@odanado
odanado deleted the fix-npm-config-and-use-npm branch October 7, 2026 03:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants