uppy/examples/sveltekit
Mikael Finstad 1fbb95da2b
improve test scripts (#6016)
1. don't run browser tests in `headless` mode by default when running
tests individually. because when writing/running tests, i usually want
to see/debug using the browser. if one still wants headless, it's as
easy as: `yarn workspace @uppy/xyz test --browser.headless`. instead
append the `headless` mode when running all tests together - it doesn't
make sense to run all projects' tests without headless mode.
2. don't always run browser tests with `watch`: watch doesn't make sense
when running multiple projects in turbo (one project just blocks the
rest watching for changes). if one still wants to run a single test with
watch mode, it's as easy as: `yarn workspace @uppy/xyz test --watch`
3. don't cache test runs: if I run the `test` command. most of the time
I want to actually run tests (not skip them if they already ran last
time)
4. output logs when running tests. it's nice to see that the tests have
actually run (also on CI)
5. when running all tests, use concurrency=1, because the tests also
includes e2e tests, running multiple browsers in parallel really just
makes the test fail on my computer (and uses a lot of memory)

current output is not very informative:

<img width="840" height="410" alt="Screenshot 2025-10-17 at 17 09 55"
src="https://github.com/user-attachments/assets/9ca8278c-f160-478c-87e2-2ef861ba4bb1"
/>

with this PR:

<img width="672" height="495" alt="Screenshot 2025-10-17 at 17 20 49"
src="https://github.com/user-attachments/assets/1339c96b-d0c1-42e1-8fa1-d5a4a36ea42a"
/>
2025-10-17 22:07:01 +08:00
..
src @uppy/svelte: fix props reactivity (#5991) 2025-10-01 16:16:47 +02:00
static Headless components (#5727) 2025-05-22 09:59:43 +02:00
test @uppy/svelte: fix props reactivity (#5991) 2025-10-01 16:16:47 +02:00
.gitignore Headless components (#5727) 2025-05-22 09:59:43 +02:00
.npmrc Headless components (#5727) 2025-05-22 09:59:43 +02:00
.stackblitzrc add typescript as a dev dep in stackblitz env (#5976) 2025-09-17 14:37:34 +05:30
package.json improve test scripts (#6016) 2025-10-17 22:07:01 +08:00
README.md Headless components (#5727) 2025-05-22 09:59:43 +02:00
svelte.config.js Migrate from Eslint/Prettier/Stylelint to Biome (#5794) 2025-07-01 14:55:41 +02:00
tsconfig.json Migrate from Eslint/Prettier/Stylelint to Biome (#5794) 2025-07-01 14:55:41 +02:00
vite.config.ts Migrate from Eslint/Prettier/Stylelint to Biome (#5794) 2025-07-01 14:55:41 +02:00
vitest.config.ts Migrate from Cypress to Vitest Browser Mode (#5828) 2025-07-28 11:27:37 +02:00

sv

Everything you need to build a Svelte project, powered by sv.

Creating a project

If you're seeing this, you've probably already done this step. Congrats!

# create a new project in the current directory
npx sv create

# create a new project in my-app
npx sv create my-app

Developing

Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:

npm run dev

# or start the server and open the app in a new browser tab
npm run dev -- --open

Building

To create a production version of your app:

npm run build

You can preview the production build with npm run preview.

To deploy your app, you may need to install an adapter for your target environment.