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

Follow-up migrate to vite (restore type tests) #1426

Merged
merged 1 commit into from
May 9, 2023

Conversation

wycats
Copy link
Contributor

@wycats wycats commented May 9, 2023

No description provided.

@wycats wycats force-pushed the chore/restore-type-tests branch from ad80727 to c4e975d Compare May 9, 2023 19:12
- Lots of lint and TypeScript cleanup
- Restructuring the .eslintrc and tsconfig.json structure
@wycats wycats force-pushed the chore/restore-type-tests branch from a4a0017 to 466e6cc Compare May 9, 2023 22:48
@wycats wycats merged commit 9cbf320 into master May 9, 2023
@wycats wycats deleted the chore/restore-type-tests branch May 9, 2023 22:48
wycats added a commit that referenced this pull request May 12, 2023
This PR was originally intended to reactivate the performance tests. My plan was to run the tests through Vite, which revealed more inconsistencies with our module setup.

This PR continues #1426 by tightening up the lints, adding a number of lints to catch problems that were stopping the built modules from working in the vite setup in the performance suite. All of the lints now run on all packages (previously, the non-published packages had significantly weaker lints), and both the published and non-published packages now share an in-repo linting plugin to keep things consistent.

It also tightens up and solidifies the infrastructure that built the packages and .d.ts files.

There's still a bit more to do to finalize the exports setup that will be driven by finishing up the performance suite work.

Since these changes are standalone improvements, I'm going to land this with the perf suite still disabled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants