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

Make it easier to diff against previous versions

Abierto
  • ¿Algo no está bien?
#2,934 0 comentarios 3 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
nuxt, typescript
Área
frontend

Línea de trabajo

Start by locating the package page UI described in the issue, especially the version header, diff link, and version sidebar. Trace how the base and target versions are selected and how the diff URL is formed. Done means users can readily compare a package version with its predecessor and understand or change the comparison direction.

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

Descripción

front
Describe the feature

In the current UI it's surprisingly difficult to diff a version against its predecessor:

  • If you're viewing the latest version (i.e., the default page) of a package then the diff link is hidden by default, so you first have to navigate to the version you want to compare against, then click the diff link there (which will then default to comparing against latest).
  • Things get even trickier for patch versions: To compare the prior version, you again first have to select the prior version, then choose the version you wanted to compare against in the first place.

I can think of a few changes that would reduce the friction:

  1. Always display the diff link. Hiding it just makes the feature more difficult to discover and doesn't do all that much to unclutter the UI.
  2. Show base and target version together. The base version (the one you're viewing) is currently displayed and selected in the top right header, while the target version is managed in the lefthand sidebar, which flips the direction of the comparison and URL parts. Showing both versions close to each other helps users understand what they are comparing, and makes it easier to add affordances to change the direction.
  3. Compare old vs new. When a user selects a target version in the UI and the relation to the base version is clear (e.g. shared semver parts), ensure that the older version becomes the base. UI affordances can still allow users to change the direction explicitly.
  4. Make the prior version more accessible. If a preceding version can be determined, either default the base to it or show it prominently in the base dropdown.
Additional information
  • Would you be willing to help implement this feature?
Final checks
Lenguaje dominante
TypeScript
Estrellas
3.6k
Forks
533
Merge medio
4 d 13 h
PR fusionados (30 d)
37

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 npmx-dev/npmx.dev

Todos los issues de npmx-dev/npmx.dev

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.