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

build: clean build script, restrict hoist of pnpm #1286

Closed
wants to merge 1 commit into from

Conversation

fi3ework
Copy link
Member

@fi3ework fi3ework commented Jan 15, 2024

Summary

  • restrict pnpm hoisted dependencies to avoid phantom deps for deps.
    • add missing dependencies after hoisting has been restricted.
    • set cwd for certain test cases to correctly resolve dependencies after hoisting has been restricted. (By the way, I believe all the current working directories should be set to the case directory instead of the current working directory, which is the workspace root now.)
    • remove the non-pure shims for ESM. Since the phantom dependencies are no longer available, the test case e2e/cases/mjs-artifact/test.mjs would fail because global.require will be set concurrently and fail due to the non-availability of the phantom dependency.
  • fix some steps in the contribution doc.

Related Links

Checklist

  • Tests updated.
  • Documentation updated.

Copy link

netlify bot commented Jan 15, 2024

Deploy Preview for rsbuild ready!

Name Link
🔨 Latest commit 44f7934
🔍 Latest deploy log https://app.netlify.com/sites/rsbuild/deploys/65a57b9363c05f0008ca6131
😎 Deploy Preview https://deploy-preview-1286--rsbuild.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -147,17 +147,17 @@ pnpm run --filter @rsbuild/some-package test

Copy link
Member

Choose a reason for hiding this comment

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

This PR contains several changes, can you split them to into separate PRs? 😄

Small PR is better for reviewing and generating changelog.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure. I'm closing this PR for now.

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.

2 participants