Skip to content
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

fix: update svelte-eslint-parser to v0.42 #874

Merged
merged 2 commits into from
Oct 16, 2024
Merged

fix: update svelte-eslint-parser to v0.42 #874

merged 2 commits into from
Oct 16, 2024

Conversation

ota-meshi
Copy link
Member

close #872

Copy link

changeset-bot bot commented Oct 16, 2024

🦋 Changeset detected

Latest commit: 8ad0802

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

This PR includes changesets to release 1 package
Name Type
eslint-plugin-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

@ota-meshi ota-meshi merged commit 457521a into main Oct 16, 2024
13 checks passed
@ota-meshi ota-meshi deleted the update--parser branch October 16, 2024 15:02
ota-meshi pushed a commit that referenced this pull request Oct 16, 2024
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## eslint-plugin-svelte@2.45.1

### Patch Changes

- [#874](#874)
[`457521a`](457521a)
Thanks [@ota-meshi](https://github.com/ota-meshi)! - fix: update
svelte-eslint-parser to v0.42

Co-authored-by: github-actions[bot] <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.

Parsing error '=>' expected when parsing typed snippets
1 participant