[BUG] Issue with CloudscapeReactTsWebsiteProject package name with InfrastructureTsProject about aws-pdk HOT 2 CLOSED

Hi Josh - you will need to be careful when naming your local workspace dependencies as frontend will actually resolve to: https://www.npmjs.com/package/frontend. The reason this occurs is that when the package.json is synthed, it will create a dependency like: frontend:"*" which will resolve to the actual frontend npm package given that is currently at a 2.x release. For most cases (where th published npm package is in the 1.x range), if your name conflicts with an npm package it will use your local dependency however in this case given frontend is in the 2.x range, that is preferred. We could potentially make a change to ensure local dependencies are resolved via workspace:*, however this is only supported in pnpm and bun so would still be problematic for yarn/npm.

The recommendation is to always scope your workspace packages to prevent conflicts with the public registry.

from aws-pdk.

oh damn, well yeah fair enough

from aws-pdk.