-
Notifications
You must be signed in to change notification settings - Fork 12
Migrate to Vite + Vitest #774
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
Conversation
🦋 Changeset detectedLatest commit: d130fa0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
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 |
6870309
to
b8f226e
Compare
fb94ea6 exists due to dequelabs/axe-core#4458 |
f33a7b0
to
9d12a98
Compare
This comment was marked as resolved.
This comment was marked as resolved.
For discussion: We could replace rollup too with https://vitejs.dev/guide/build.html#library-mode |
is there a reasonable way to sync certain configs across projects? e.g. I see parts of eslint config changed here to include the same options as standalone (but also more) and also options are in a different order. |
Not sure for vite/vitest, but for eslint we can make a ruleset and use that just like we do with other eslint plugins. There is already a ticket for this. |
Did/can you check if any of the warnings produces by |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
92795de
to
6cf1177
Compare
see NEO-689 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Outline the vitest migration Add changesets Fix typos Fix missing dependencies Remove obsolete jest config Remove more old references to jest Use our own more simple vitest-axe extension Adjust the i18next-parser.config.js Ensure the coverage dependency is made a dependency and ensure we are not running in commonjs mode Use the correct axe import Fix vite config for the example widget and the dedup of it. Also fix the exports in the package jsons Ensure we run cleanup from @testing-library/react after each test to have a clean state Exclude the build and lib folders to prevent falsely detected tests Run check-api-report to update the testing library Ensure we don't mix act from different dependencies and just always use the one from react Fixup review items and update docs as needed Signed-off-by: MTRNord <[email protected]>
Signed-off-by: Michael Weimann <[email protected]>
Signed-off-by: Michael Weimann <[email protected]>
3878063
to
9d93427
Compare
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please update containers/widget-server/README.md regarding CRA. there is another mention in the ADRs which I think we can keep.
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: Michael Weimann <[email protected]>
Signed-off-by: Michael Weimann <[email protected]>
Ports for the example widget and preview are now: 5173 (http) and 5174 (https). Lets use the next ports for neoboard etc. then. If preview and dev should be different ports, leave a comment. I don't have a strong opinion on this. |
Signed-off-by: Michael Weimann <[email protected]>
done |
Signed-off-by: Michael Weimann <[email protected]>
Signed-off-by: Michael Weimann <[email protected]>
Signed-off-by: Michael Weimann <[email protected]>
✔️ Checklist
Signed-off-by
line in the message (more info).