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

Migrated to vitest #571

Closed

Conversation

mattpocock
Copy link
Contributor

@mattpocock mattpocock commented Aug 20, 2024

Fewer dependencies, more modern tooling, in the same spirit as #570

Copy link

changeset-bot bot commented Aug 20, 2024

⚠️ No Changeset found

Latest commit: 591e861

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

]

type ExpecteResult = Result<[ string, number, boolean ], (string | number | boolean)[]>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Looks like prettier formatting

"strictNullChecks": true,
"strictFunctionTypes": true,
"declaration": true,
"skipLibCheck": true,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Only change here is adding skipLibCheck: true to remove an erroneous error when I upgraded

Copy link
Owner

@supermacro supermacro Sep 6, 2024

Choose a reason for hiding this comment

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

I was curious to know what the issues were. Here they are (at least for posterity):

image

... interestingly WeakKey is infact a ts builtin:

image

As for the "Cannot find module 'rollup/parseAst' or its corresponding type declarations." issue, I came across this thread:

rollup/rollup#5199

Any thoughts @dmmulroy

Copy link
Collaborator

Choose a reason for hiding this comment

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

vitest-dev/vitest#4921

WeakKey is available in TS >= 5.2

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Errors thrown in node_modules don't matter - it's not code that we control. If there are no errors on install (i.e. peerDeps are all good) then we're happy.

@mattpocock mattpocock mentioned this pull request Aug 20, 2024
10 tasks
Copy link
Contributor

@dmmulroy dmmulroy left a comment

Choose a reason for hiding this comment

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

lgtm - thanks Matt

@m-shaka @supermacro I am much in favor of this change and have been using vitest by default for a year or so now

@supermacro
Copy link
Owner

Love this. Thank you 🙌

@mattpocock
Copy link
Contributor Author

@supermacro Getting the same error as here on this PR

@dmmulroy
Copy link
Contributor

dmmulroy commented Oct 9, 2024

@mattpocock @m-shaka Can we get tests/CI passing and get this in?

@supermacro supermacro mentioned this pull request Oct 23, 2024
@supermacro supermacro closed this Oct 23, 2024
@supermacro
Copy link
Owner

Too many conflicts, easier to just create a new branch. See #597

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.

4 participants