Skip to content

chore: allow testing in production env#16840

Merged
Rich-Harris merged 2 commits intomainfrom
production-tests
Jan 29, 2026
Merged

chore: allow testing in production env#16840
Rich-Harris merged 2 commits intomainfrom
production-tests

Conversation

@7nik
Copy link
Contributor

@7nik 7nik commented Sep 25, 2025

Add the ability to set DEV to false for test.
It's supposed to be

if (config.production) fn = run_in_production(fn);

But due to vitest-dev/vitest#7712 unmocking doesn't work, so instead such tests are moved to the end of the queue.

This should allow adding the correct tests to #16724.

Before submitting the PR, please make sure you do the following

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • Prefix your PR title with feat:, fix:, chore:, or docs:.
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.
  • If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

  • Run the tests with pnpm test and lint the project with pnpm lint

@changeset-bot
Copy link

changeset-bot bot commented Sep 25, 2025

⚠️ No Changeset found

Latest commit: 872fa3a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Contributor

Playground

pnpm add https://pkg.pr.new/svelte@16840

Copy link
Member

@Rich-Harris Rich-Harris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

neat!

@Rich-Harris Rich-Harris merged commit ffd65e9 into main Jan 29, 2026
18 checks passed
@Rich-Harris Rich-Harris deleted the production-tests branch January 29, 2026 02:56
7nik added a commit that referenced this pull request Jan 29, 2026
Rich-Harris pushed a commit that referenced this pull request Jan 29, 2026
* Revert "chore: allow testing in production env (#16840)"

This reverts commit ffd65e9.

* new approach
7nik added a commit that referenced this pull request Jan 30, 2026
* Revert "chore: allow testing in production env (#16840)"

This reverts commit ffd65e9.

* new approach
7nik added a commit that referenced this pull request Feb 4, 2026
* fix: emit `each_key_duplicate` error in production

* fix: preserve key

* Update packages/svelte/src/internal/client/dom/blocks/each.js

Co-authored-by: Rich Harris <rich.harris@vercel.com>

* Update packages/svelte/src/internal/client/dom/blocks/each.js

Co-authored-by: Rich Harris <rich.harris@vercel.com>

* fix: ensure keys are validated

* fix silly test name

* fix: cover other case of duplicate keys

* emit error on hydration

* ensure the error is handled

* drop useless tests

* unused

* finish merge

* add lost check back

* chore: bump playwright (#17565)

* chore: bump playwright

* maybe this will help somehow?

* err whatever

* fix

* chore: allow testing in production env 2 (#17590)

* Revert "chore: allow testing in production env (#16840)"

This reverts commit ffd65e9.

* new approach

* fix: handle renderer.run rejections (#17591)

* fix: handle renderer run rejections

* add test

* changeset

* simplify

* explanatory comment

---------

Co-authored-by: Antonio Bennett <abennett@mabelslabels.com>
Co-authored-by: Rich Harris <rich.harris@vercel.com>

* fix: only create async functions in SSR output when necessary (#17593)

* fix: only create async functions in SSR output when necessary

* actually...

* simplify generated code a bit more

* simplify

* fix: merge consecutive text nodes during hydration for large text content (#17587)

* fix: merge consecutive text nodes during hydration for large text content

Fixes #17582

Browsers automatically split text nodes exceeding 65536 characters into
multiple consecutive text nodes during HTML parsing. This causes hydration
mismatches when Svelte expects a single text node.

The fix merges consecutive text nodes during hydration by:
- Detecting when the current node is a text node
- Finding all consecutive text node siblings
- Merging their content into the first text node
- Removing the extra text nodes

This restores correct hydration behavior for large text content.

* add test, fix

* fix

* fix

* changeset

---------

Co-authored-by: Miner <miner@example.com>
Co-authored-by: Rich Harris <rich.harris@vercel.com>

* Version Packages (#17585)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Revert "drop useless tests"

This reverts commit 65f77ef.

* update tests

* fix test

* we don't need to expose this function any more

* figured it out... we cant have errors during reconcile

* simplify

* tweak

* unused

* revert no-longer-needed change

* unused

---------

Co-authored-by: Rich Harris <rich.harris@vercel.com>
Co-authored-by: Antonio Bennett <31296212+Antonio-Bennett@users.noreply.github.com>
Co-authored-by: Antonio Bennett <abennett@mabelslabels.com>
Co-authored-by: FORMI <239411042+Richman018@users.noreply.github.com>
Co-authored-by: Miner <miner@example.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants