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

Question: Any projects based on this that ARE trying to be complete like JSDOM?

Abierto
#198 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
javascript, react
Área
testing, web-dev

Línea de trabajo

Esta es una pregunta exploratoria, no un cambio con un alcance definido, y no menciona archivos ni pruebas del repositorio. Empieza revisando cómo LinkeDOM gestiona Location, navigator.clipboard y Document.createRange(), y determina después si un proyecto existente o una nueva capa de polyfill debería proporcionar el comportamiento ausente del navegador. Para darlo por terminado sería necesario acordar el alcance y el plan de implementación.

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

Descripción

This is a cool project! Context: I'm dealing right now with trying to figure out how to have tests for React components that don't take forever to run, can live in a clean plain old node environment instead of Jest's parallel universe, use tap's API instead of the code poetry like expect(thing).toHave.something('i can never remember this junk').that.isnt.Null(), etc.

I have it working now, but the big bottleneck is jsdom. Every component test takes like 5-10 seconds to spin up, at minimum, for a test that runs in 50ms or less. If they do anything interesting with the dom (which a lot of them do), it gets much worse. I'm starting to see why jest runs tests in the parallel universe that it does.

It seems like @testing-library/react and @testing-library/userevents can almost work, but there are some missing pieces (by design, I realize). I totally understand not wanting to add those pieces to linkedom, and agree with that principle entirely.

So the question is, is there a project you're aware of that uses linkedom under the hood, but then does add that extra stuff? Some of what seem to be missing that I've run into:

  • Location isn't set. (Can kinda hack around it by setting window.location to a URL object, which is close enough, but a proper Location polyfill would obviously be needed for anything doing actual navigation.)
  • Navigator has userAgent, but navigator.clipboard is missing.
  • Document.createRange() returns an object that doen'st have setStart and setEnd methods.

I'm thinking it'd be possible to create a set of polyfills for all these things, and probably end up with something that would really only lack some of the finer points of JSDOM's tree structure, but still be close enough to simulate a browser for react testing.

Is someone doing this already? Or, if not, is there some reason you know of why linkedom isn't a suitable base for something like this?

Thanks!

Lenguaje dominante
HTML
Estrellas
2.1k
Forks
104
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 WebReflection/linkedom

Todos los issues de WebReflection/linkedom

Issues similares

Más issues de Testing & QA

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.