Skip to content
New issue

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

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

Already on GitHub? # to your account

ci(e2e): fix SvelteKit test #6345

Closed
wants to merge 1 commit into from
Closed

ci(e2e): fix SvelteKit test #6345

wants to merge 1 commit into from

Conversation

merceyz
Copy link
Member

@merceyz merceyz commented Jun 14, 2024

What's the problem this PR addresses?

create-svelte no longer has a next tag.

How did you fix it?

Stop specifying the tag.

Checklist

  • I have read the Contributing Guide.
  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

@merceyz merceyz requested a review from arcanis as a code owner June 14, 2024 21:57
@merceyz merceyz changed the title ci(e2e): fix Svelte test ci(e2e): fix SvelteKit test Jun 14, 2024
@merceyz merceyz marked this pull request as draft June 14, 2024 22:05
@merceyz merceyz mentioned this pull request Aug 1, 2024
3 tasks
@merceyz
Copy link
Member Author

merceyz commented Aug 1, 2024

Closing in favour of #6428

@merceyz merceyz closed this Aug 1, 2024
@merceyz merceyz deleted the merceyz/ci/e2e-svelte branch August 1, 2024 13:50
arcanis pushed a commit that referenced this pull request Oct 15, 2024
## What's the problem this PR addresses?

The SvelteKit E2E test has been failing

## How did you fix it?

- `create-svelte` discontinued the `next` dist-tag, use `latest` instead
- I don't know how it was but `yes` cannot defeat `create-svelte`
interactivity now, so I just use its node API instead
- Also added a TypeScript test

The test should still be failing due to
sveltejs/kit#11433 (comment), but
at least it is an actual failure of the E2E test, not of our setup.
:shrug:

Closes #6345

## Checklist

<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).

<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [x] I have set the packages that need to be released for my changes to
be effective.

<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.

---------

Co-authored-by: Kristoffer K. <merceyz@users.noreply.github.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant