-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
chore(compiler): migration to rollup + vitest (prep work for CJS/ESM dual bundles) #8826
Draft
mmaietta
wants to merge
9
commits into
master
Choose a base branch
from
explore/vitest-rollup-2
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 77b6700 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 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 |
0db5c46
to
3af1fcc
Compare
…ackage for esm+cjs. This PR is the initial setup/migration to the new bundler + testing framework. Overall, vitest was a simple setup but rollup was encountering cyclical dependency issues, so a minor extraction of various functions to separate files was needed. _Note: All moved functions that were originally exposed via API to end-user developers have remained the same._ Additional changes: - `require` is now `await import` which required `createTargets` to be migrated to `async`. This was fine as the caller of `createTargets` is already an async function, so this simply was a matter of adding `await` to `createTargets` invocation - `ifAll` test helper function was removed. It would be triggered via env var ALL_TESTS, but we haven't used that env var in years. - Added ts-node to run `checkDeps` and `generate-schema` since we don't compile the `test` dir with rollup, vitest automatically is able to run it as-is.
28f0381
to
144b241
Compare
…vitest-rollup-2 # Conflicts: # test/src/HoistedNodeModuleTest.ts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The end goal here is to see if we can enable dual publishing of the package for esm+cjs. This PR is the initial setup/migration to the new bundler + testing framework.
Overall, vitest was a simple setup but rollup was encountering cyclical dependency issues, so a minor extraction of various functions to separate files was needed. Note: All moved functions that were originally exposed via API to end-user developers have remained the same.
Additional changes:
require
is nowawait import
which requiredcreateTargets
to be migrated toasync
. This was fine as the caller ofcreateTargets
is already an async function, so this simply was a matter of addingawait
tocreateTargets
invocationifAll
test helper function was removed. It would be triggered via env var ALL_TESTS, but we haven't used that env var in years.checkDeps
andgenerate-schema
since we don't compile thetest
dir with rollup, vitest automatically is able to run it as-is.