Oxlint

[TaylorBeeston]

Overview

🎟 Relevant Jira Issues

📚 What is the context and goal of this PR?

This PR replaces ESLint with Oxlint! =) (https://oxc.rs/docs/guide/usage/linter.html)

🥴 TL; RL:

Claude Code and I went through and deleted all ESLint stuff and replaced it with Oxlint! I then ran
the linter through the whole repo and fixed all lint errors/warnings!

💡 Feature Breakdown (screenshots & videos encouraged!)

🛠 Important tradeoffs made:

You'll need to set up support for Oxlint in your editor! I think we all use VSCode/a fork of it now, so it
should auto-prompt you when you check out this PR. I haven't set up oxlint in neovim yet, so no help
there (yet).

🔍 Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Chore (refactor, documentation update, etc)

💳 Does This Create Any New Technical Debt? ( If yes, please describe and add JIRA TODOs )

• No
• Yes

Testing

🔬 How Can Someone QA This?

pnpm i && pnpm lint

📱 🖥 Which devices would you like help testing on?

🧪 Code Coverage

No new tests, but all current tests pass!

Documentation

📜 Gitbook

📊 Storybook

✅ PR Checklist

• Related to a Jira issue (create one if not)
• My code follows style guidelines (eslint / prettier)
• I have manually tested common end-2-end cases
• I have reviewed my code
• I have commented my code, particularly where ambiguous
• New and existing unit tests pass locally with my changes
• I have made corresponding changes to gitbook documentation

🚀 Ready to squash-and-merge?:

• Code is backwards compatible
• There is not a "Do Not Merge" label on this PR
• I have thoughtfully considered the security implications of this change.
• This change does not expose new public facing endpoints that do not have authentication

[changeset-bot]

🦋 Changeset detected

Latest commit: 188e983

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

This PR includes changesets to release 38 packages

Name	Type
@learncard/simple-signing-service	Patch
@learncard/simple-signing-client	Patch
@learncard/learn-cloud-service	Patch
@learncard/network-brain-service	Patch
@learncard/network-brain-client	Patch
@learncard/learn-cloud-client	Patch
@learncard/simple-signing-plugin	Patch
@learncard/network-plugin	Patch
@learncard/claimable-boosts-plugin	Patch
@learncard/create-http-bridge	Patch
@learncard/did-web-plugin	Patch
@learncard/dynamic-loader-plugin	Patch
learn-card-discord-bot	Patch
@learncard/vc-templates-plugin	Patch
@learncard/learn-cloud-plugin	Patch
@learncard/snap-chapi-example	Patch
@learncard/helpers	Patch
@learncard/encryption-plugin	Patch
@learncard/expiration-plugin	Patch
@learncard/learn-card-plugin	Patch
@learncard/snap-example-dapp	Patch
@learncard/types	Patch
@learncard/ethereum-plugin	Patch
@learncard/react	Patch
@learncard/core	Patch
@learncard/init	Patch
@learncard/ceramic-plugin	Patch
@learncard/crypto-plugin	Patch
@learncard/didkey-plugin	Patch
@learncard/didkit-plugin	Patch
@learncard/vc-api-plugin	Patch
@learncard/meta-mask-snap	Patch
@learncard/chapi-example	Patch
@learncard/chapi-plugin	Patch
@learncard/vpqr-plugin	Patch
@learncard/idx-plugin	Patch
@learncard/vc-plugin	Patch
@learncard/cli	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

[netlify]

❌ Deploy Preview for learn-card-chapi-example failed. Why did it fail? →

Name	Link
🔨 Latest commit	188e983
🔍 Latest deploy log	https://app.netlify.com/projects/learn-card-chapi-example/deploys/68531742b5b6cb0008daace7

[netlify]

✅ Deploy Preview for learncarddocs canceled.

Name	Link
🔨 Latest commit	188e983
🔍 Latest deploy log	https://app.netlify.com/projects/learncarddocs/deploys/685317422b6c7d0008e8d171

[gitstream-cm]

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

[gitstream-cm]

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

[gitstream-cm]

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.