Open lznbuild opened 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"?
Execute the command "yarn workspaces info" in my project, and I can see the dependencies between packages
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"?