Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Check for pnpm v10 `pnpm.onlyBuiltDependencies` for certain packages

Abierto
#620 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
next.js, typescript

Línea de trabajo

Start by tracing the existing Preflight checks and how they read package.json. Identify packages such as sharp and bcrypt that require lifecycle builds, then validate the pnpm.onlyBuiltDependencies configuration against those packages. Done means pnpm v10 projects receive a useful failure or warning when required entries are missing.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Alternative to https://github.com/upleveled/eslint-config-upleveled/issues/488

Currently, some lifecycle scripts (build scripts) of packages like sharp and bcrypt are not allowed in pnpm v10, and result in errors like the following Ignored build scripts error:

$ pnpm install
Lockfile is up to date, resolution step is skipped
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +814
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 814, reused 0, downloaded 69, added 66

...

Ignored build scripts: sharp. Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts.

Done in 13.8s

A student not including sharp in their Next.js project will mostly appear to work properly, but pages will most likely be slow to load, due to Next.js falling back to slower non-native image optimization.

To avoid this, add a Preflight check to:

  1. Check package.json for packages which should be built, like sharp and bcrypt
  2. Make sure that students have configured the pnpm.onlyBuiltDependencies correctly (like the example below) for such packages
{
  "pnpm": {
    "overrides": {
      "@emotion/react": "11.14.0",
      "@emotion/styled": "11.14.0",
      "@tailwindcss/node": "4.0.1",
      "@tailwindcss/oxide": "4.0.1",
      "@types/react": "19.0.8",
      "@types/react-dom": "19.0.3"
    },
    "patchedDependencies": {
      "next": "patches/next.patch"
    },
    "onlyBuiltDependencies": [
      "sharp"
    ]
  }
}
Lenguaje dominante
TypeScript
Estrellas
14
Forks
3
Merge medio
3 d 13 h
PR fusionados (30 d)
8

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de upleveled/preflight

Todos los issues de upleveled/preflight

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.