neuron-explorer
Qwen3.5‑4B 전용 조향형 뉴런 탐색기, 모든 MLP 뉴런을 밀어 결과를 보관·탐색
Bootstrap v6 테스트 환경
Test bench for Bootstrap v6: every docs example, real app screens and bug reproductions on one Vite site, with 40+ configs, visual/console/smoke/accessibility tests in three engines, and a nightly can
개발 도구HTML · JavaScriptGitHub @julien-deramond온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Test bench for Bootstrap v6: every docs example, real app screens and bug reproductions on one Vite site, with 40+ configs, visual/console/smoke/accessibility tests in three engines, and a nightly canary that tracks v6-dev.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A test bench for Bootstrap v6. It puts every docs example, realistic app screens and bug reproductions on one Vite site, compiles Bootstrap from source under 40+ configs, and runs a set of browser tests and audits against each new upstream commit.README 전문 보기 ↗A test bench for Bootstrap v6 (the main branch of twbs/bootstrap, called v6-dev until 2026-10-08). It puts every docs example, realistic app screens and bug reproductions on one Vite site, compiles Bootstrap from source under 40+ configs, and runs a set of browser tests and audits against each new upstream commit.
$enable-* options, custom color modes, partial builds), switched live on any pagemain, runs every check and opens a pull request with what changednpm install
npm run dev
Open http://localhost:5173. The home page lists every page, with search and filters. Press Ctrl+K on any page to jump to another.
Out of the box, the playground renders Bootstrap's defaults. To try a change, edit the working copy in src/styles/ (Sass options, custom rules or CSS tokens) and it hot-reloads, or pick a saved config from the toolbar. See Customizing.
Bootstrap is installed from GitHub (twbs/bootstrap#main, pinned by the lockfile). To test a branch you're working on instead:
cp .env.example .env.local # BOOTSTRAP_PATH=../twbs/bootstrap
npm run dev
Sass and JavaScript then come from that checkout, and edits there hot-reload too. See Bootstrap versions and updates.
| Command | What it does |
|---|---|
npm run dev | Starts the dev server |
npm run new-issue <name> [-- --config <name>] [--from <page>#<id>] | Creates a reproduction in issues/<name>/, optionally from a kitchen sink example |
npm run import-issue <n> [-- --config <name>] [--force] | Creates issues/<n>/ from a twbs/bootstrap issue or pull request, its code cleaned and inert until reviewed |
npm run export-issue <name> | Exports a reproduction as one HTML file and a StackBlitz project, for upstream maintainers |
npm run save-config <name> / use-config <name> | Saves the working copy as a config, or loads one |
npm run update-bootstrap | Moves to the latest main commit and runs the checks that need no browser |
npm run test:visual [-- -u] | Compares every page with its screenshot baselines |
npm run test:console / test:smoke / test:a11y | Console crawl, interaction smoke tests, accessibility scan |
The test suites need Playwright's browsers once: npx playwright install chromium (add firefox webkit for the other engines). docs/README.md lists every script.
Bootstrap bugs found here are tracked as issues in this repository, labeled upstream until they're reported to twbs/bootstrap, then upstream-reported, then upstream-fixed. The checks allowlist a known bug only with its tracking issue, and fail once it's fixed so the entry gets removed. CLAUDE.md has the full workflow and the project's conventions.
MIT. The starter screens and kitchen sink examples are adapted from Bootstrap (MIT). The real screens are adapted from shadcn/ui (MIT, see screens/LICENSE-shadcn-ui.md).