How teselagen/tg-oss works
Project type and purpose
• This is a TypeScript/JavaScript monorepo (managed by Nx) that hosts multiple related but independent packages for bioinformatics and UI tooling.
• Its primary purpose is to provide:
• @teselagen/ove, a React-based vector editor for viewing/editing DNA/AA sequences
• @teselagen/ui, a reusable React component library
• Utility libraries (@bio-parsers, @sequence-utils, @range-utils, @file-utils) for parsing, manipulating sequences and files
• Small demo and loader tools (bounce-loader, uploader, example-demos, shared-demo)
• CI/CD pipelines (GitHub Actions) run linting, unit tests (Jest/Vitest), E2E tests (Cypress/Playwright) and publishing.
File structure
• Top-level config files: nx.json, tsconfig.base.json, jest.config.ts, babel.config.json, .eslintrc.json, .prettierrc, .github/workflows/*
• /packages – each subfolder is an independent npm package project.json + tsconfig.json + source, tests, demo or config files
• bio-parsers
• sequence-utils
• range-utils
• file-utils
• ove
• ui
• bounce-loader
• uploader
• shared-demo
• /example-demos & /packages/*/demo – small demo apps showing usage of the libraries
• /tools/scripts – custom publishing scripts
• Root workflows: cypress.yml, playwright.yml, update_gh_pages.yml
README
• Lists the six primary packages, their purpose, demo URLs, publish scripts via nx run <pkg>:publish
• Emphasizes monorepo publishing strategy
Detail without overthinking
• Both technical infra (Nx, CI) and application layers (libs, core editor, demos)
This structure will give a comprehensive, accurate architectural overview of the monorepo, its constituent packages, their interdependencies, and the DevOps processes that bind them together.