Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

PR E: Retire TikZ, keep and fix the old graph renderer

Open
  • Is something wrong?
#377 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
d3, javascript, node.js, react, redux
Domain
frontend

Research direction

This is part of #351 and depends on #354 and #357. Read those issues and check where LaTeXGraphSvgReact.js, StandardGraphSvgReact.js, node-tikzjax, and the GraphLaTeX registry type are used; verify Redux no longer sends GraphLaTeX and the new renderers cover DFA, NFA, and Clique before removing the old pieces. Done means the retired renderer and dependency are removed without breaking graph rendering or the registry.

Written by the indexing model from the issue text.

Description

enhancement

Part of #351. Once DFA, NFA and Clique render with the new Automaton and Graph renderers:

  • Remove LaTeXGraphSvgReact.js and node-tikzjax (its svgo dependency carries advisories GHSA-2p49-hgcm-8545, GHSA-w27v-7q3p-w38r and GHSA-4vpr-x523-8j87; TikZ source is built from problem data)
  • Keep StandardGraphSvgReact.js as the old graph renderer, alongside the new ones, so the old path stays available. Fix its two bugs instead of removing it: it runs d3.scaleLinear over string weights like "a,b", and it builds DOM ids with .replace("!","NOT"), which only replaces the first ! and collides when two graphs are mounted.
  • Remove the GraphLaTeX type from the registry once Redux stops sending it

TikZ is retired only for its drift and vulnerability problems. The old graph renderer stays (decided Oct 19, 2026).

Depends on: #354, #357.

Dominant language
JavaScript
Stars
3
Forks
18
Avg merge
1d 3h
Merged PRs (30d)
35

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ReduxISU/Redux_GUI

All issues in ReduxISU/Redux_GUI

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.