mirror of https://github.com/buster-so/buster.git
* update files for use with biom
* fix prettier formats
* minor biome fixes
* fix additional files
* update linting rules
* fix additional linting errors
* fix linting errors
* update lib
* run check in the lib direcotyr
* update some linting errors
* fix problems
* move addtional files to stricter linting
* fix imports and linting errors
* update some biome settings
* fix query parser
* quick wins
* update files
* fix addtional things
* fix context files
* update additional biome files
* fix additional files
* biome fixes
* fixin files
* fix broken
* fix additional files and problems
* fix biome buster stuff
* fix helpers and
* stricter linting
* fixed
* fix missing types
* fix linting
* remove missing imports
* update more biome test stuff
* update fixes
* update imports
* more updates
* fix some linting errors
* fix broken children as prop errors
* lint ci
* update lint check
* Update package.json
* Update next.config.mjs
* fix some broken tests
* update some tests
* chore(versions): bump api to v0.1.16; bump web to v0.1.16; bump cli to v0.1.16 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update web-unit-tests.yml
* fix some tests
* chore(versions): bump api to v0.1.17; bump web to v0.1.17; bump cli to v0.1.17 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* update ignore files
* chore(versions): bump api to v0.1.18; bump web to v0.1.18; bump cli to v0.1.18 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update web-lint.yml
* chore(versions): bump api to v0.1.19; bump web to v0.1.19; bump cli to v0.1.19 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* update boime package settings
* chore(versions): bump api to v0.1.20; bump web to v0.1.20; bump cli to v0.1.20 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* save to dropdown bug fixes
* update console logs
* update chart animation
* chore(versions): bump api to v0.1.21; bump web to v0.1.21; bump cli to v0.1.21 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* update build
* chore(versions): bump api to v0.1.22; bump web to v0.1.22; bump cli to v0.1.22 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* additinal updates for biome 2
* update imports
* chore(versions): bump api to v0.1.23; bump web to v0.1.23; bump cli to v0.1.23 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* final updates
* chore(versions): bump api to v0.1.24; bump web to v0.1.24; bump cli to v0.1.24 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update dashboard-updates.test.ts
* chore(versions): bump api to v0.1.25; bump web to v0.1.25; bump cli to v0.1.25 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* crazy fix
* chore(versions): bump api to v0.1.26; bump web to v0.1.26; bump cli to v0.1.26 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* more attempts for stable tests
* chore(versions): bump api to v0.1.27; bump web to v0.1.27; bump cli to v0.1.27 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* update tests
* split the test off
* chore(versions): bump api to v0.1.28; bump web to v0.1.28; bump cli to v0.1.28 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update pie-styling-updates.spec.ts
* Create web-e2e-tests-optimized.yml
* chore(versions): bump api to v0.1.29; bump web to v0.1.29; bump cli to v0.1.29 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* update tests
* chore(versions): bump api to v0.1.30; bump web to v0.1.30; bump cli to v0.1.30 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update web-e2e-tests-optimized.yml
* chore(versions): bump api to v0.1.31; bump web to v0.1.31; bump cli to v0.1.31 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update web-e2e-tests-optimized.yml
* chore(versions): bump api to v0.1.32; bump web to v0.1.32; bump cli to v0.1.32 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update web-e2e-tests-optimized.yml
* chore(versions): bump api to v0.1.33; bump web to v0.1.33; bump cli to v0.1.33 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update web-e2e-tests-optimized.yml
* chore(versions): bump api to v0.1.34; bump web to v0.1.34; bump cli to v0.1.34 [skip ci]
* chore: update tag_info.json with potential release versions [skip ci]
* Update web-e2e-tests-optimized.yml
* Update web-e2e-tests-optimized.yml
* Revert "Update web-e2e-tests-optimized.yml"
This reverts commit
|
||
---|---|---|
.. | ||
.cursor/rules | ||
.storybook | ||
playwright-tests | ||
public | ||
src | ||
.dockerignore | ||
.env.development | ||
.gitattributes | ||
.gitignore | ||
.nvmrc | ||
Dockerfile | ||
Makefile | ||
README.md | ||
biome.json | ||
chromatic.config.json | ||
globals.d.ts | ||
next.config.mjs | ||
package-lock.json | ||
package.json | ||
playwright.config.ts | ||
postcss.config.mjs | ||
tsconfig.json | ||
vitest.config.ts | ||
vitest.setup.ts |
README.md
This is a Next.js project bootstrapped with create-next-app
.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx
. The page auto-updates as you edit the file.
This project uses next/font
to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.