8000 fix: make deriveds on the server lazy again by dummdidumm · Pull Request #15964 · sveltejs/svelte · GitHub
[go: up one dir, main page]

Skip to content

fix: make deriveds on the server lazy again #15964

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 22, 2025
Merged

Conversation

dummdidumm
Copy link
Member
@dummdidumm dummdidumm commented May 20, 2025

Fixes a regression introduced in #15820: deriveds need to be lazily called on the server, too, since they can close over variables only later defined

Fixes #15960

After having opened this I realized that the new behavior fixed #15672 , so I guess we need to adjust this PR to keep that fixed. and this PR makes sure it stays fixed

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 8000 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

Fixes a regression introduced in #15820: deriveds need to be lazily called on the server, too, since they can close over variables only later defined

Fixes #15960
Copy link
changeset-bot bot commented May 20, 2025

🦋 Changeset detected

Latest commit: 5ba3572

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

Not sure what this means? Click here to learn what changesets are.

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

@svelte-docs-bot
Copy link

8000
Copy link
Contributor

Playground

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

@paoloricciuti
Copy link
Member

I think we need to at least change

this.foo() = 3;

be

this.foo(3);

However I wonder what are the implications of doing an assignment in the constructor (that now needs to create a new derived)


return function (new_value) {
if (arguments.length === 0) {
return updated_value ?? fn();
Copy link
Member Author

Choose a reason for hiding this comment

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

This calls the function on every invocation now, we should wrap it with once above

Copy link
Member

Choose a reason for hiding this comment

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

It should be called everytime or else the value will not change on reassignment no?

Copy link
Member

Choose a reason for hiding this comment

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

If you are talking about fn it the stateful value it's dependent on changes it should be rerun no?

Copy link
Member Author

Choose a reason for hiding this comment

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

We only called fn once previously and that was fine and declared as the behavior on the server. The bug introduced was that it was now called eagerly, not lazily

Copy link
Member

Choose a reason for hiding this comment

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

I know but I still think this would be the better behavior (which I was also trying to fix on #14977 )...I guess in this case is still better to wrap fn in once however

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll add a change to wrap it in once then we can think about this in #14977 separately, for now we need to fix this critical bug

@Rich-Harris Rich-Harris merged commit ac046df into main May 22, 2025
13 checks passed
@Rich-Harris Rich-Harris deleted the lazy-derived-server branch May 22, 2025 21:07
@github-actions github-actions bot mentioned this pull request May 22, 2025
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.

Private $derived class fields break SSR [SERVER] writable $derived in class results invalid setter expression
4 participants
0