-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
perf: switch to yarn 3 + dedupe dependencies #20964
perf: switch to yarn 3 + dedupe dependencies #20964
Conversation
This doesn’t work yet: postinstall scripts cause a recursive install loop
For some reason, after the Yarn v3 upgrade, some previously omitted TS errors are now visible. This commit fixes them.
During `yarn dedupe`, Yarn settled down on Blueprint Core v3.43. However, the current version of @blueprintjs/datetime relies on an import from @blueprintjs/core that’s not present in v3.43. In Yarn 1 setup, this used to work due to an accident: @blueprintjs/datetime installed a newer (3.47) version of @blueprintjs/core, which had the necessary import. Now that we deduped the versions, this doesn’t work anymore. This commit fixes this by upgrading the Blueprint Core to v3.47.
Welcome to the Appsmith community! Thank you for your first pull request and making this project better. 🤗 Please make sure that you raise a review request so your code change does not go unnoticed. |
@iamakulov is attempting to deploy a commit to the Appsmith Team on Vercel. A member of the Team first needs to authorize it. |
We moved package.json one level higher, and that somehow made webpack preference node_modules/entities over src/entities. The previous behavior was weird. (I can’t figure out *why* webpack would prefer src/entities, as it wasn’t configured [1] to do so.) But this commit fixes that. [1] https://github.com/facebook/create-react-app/blob/d960b9e38c062584ff6cfb1a70e1512509a966e7/packages/react-scripts/config/webpack.config.js#L306-L312
18006c3
to
e249cab
Compare
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4291192683. |
@@ -8,7 +8,7 @@ | |||
}, | |||
"cracoConfig": "craco.dev.config.js", | |||
"dependencies": { | |||
"@blueprintjs/core": "^3.36.0", | |||
"@blueprintjs/core": "^3.43.0", |
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.
Blueprint is updated here, might need to check if everything is working as expected.
ea30c41
to
901056a
Compare
This: - adds `rts` into the list of workspaces - changes the build steps for `rts` to copy both the global and the workspaces’ node_modules into `dist`
This commit: - updates the icon names in the IconSelectControl tests. This was done because with the @blueprintjs/icon update, the control now has more icons, so the previous className checks don’t work anymore (now: https://user-images.githubusercontent.com/2953267/222846934-3b8ad6ae-8cf5-4de4-b5d0-cd3b7ef4234e.png; before: https://user-images.githubusercontent.com/2953267/222846936-bae05b25-dfc6-47cc-934d-3c1cb0d4080d.png) - switches the tests to snapshots: this makes it much easier to update icon names in case of future @blueprintjs/icon upgrades
This upgrades the build script to use Yarn 3 properly. This was missed while incorporating appsmithorg#20776 into appsmithorg#20964.
The package got upgraded during #20964. The reason we’re downgrading is we want to keep the list of icons we support fixed. If we ever have to migrate off @blueprintjs/icons, we’ll have to manually maintain all icons that are available in the package.
Description
This PR:
shared/ast
to Yarn Workspacesbuild-shared-dep.js
,install-dependencies.js
, etc logic)shared/ast
is now rebuilt only when needed instead of on everyyarn add
)patch-package
with Yarn’s native package patching@blueprintjs/core
installed?)yarn dedupe
run on every installApart from DX improvements, this also makes the bundle almost 10% smaller (−870 kB, 9.01 → 8.14 MB minified).
Type of change
How Has This Been Tested?
Test Plan
Issues raised during DP testing
Checklist:
Dev activity
QA activity: