yarnpkg / yarn

The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
https://classic.yarnpkg.com
Other
41.4k stars 2.73k forks source link

I hope I can feel this when change symlink's file content #8896

Open lznbuild opened 1 year ago

lznbuild commented 1 year ago

Execute the command "yarn workspaces info" in my project, and I can see the dependencies between packages

{
  "package-a": {
    "location": "packages/package-a",
    "workspaceDependencies": [common-package],
    "mismatchedWorkspaceDependencies": []
  },
  "common-package": {
    "location": "packages/common-package",
    "workspaceDependencies": [],
    "mismatchedWorkspaceDependencies": []
  },
  "package-b": {
    "location": "packages/package-b",
    "workspaceDependencies": [common-package],
    "mismatchedWorkspaceDependencies": []
  }
}

I have a question. In the local development environment, what should I do to sense the change of "common-package" file content in "package-b" and "package-a" ?

Like "Hot Module Replacement"?