What
Declare @swr-data-lab/components as a peer dependency (^4.0.0) of @swr-data-lab/components-map. The "*" devDependency stays, for the workspace link.
Why
19 modules in components-map/dist import @swr-data-lab/components, but it was only listed as a devDependency. Installing components-map on its own left those imports unresolved. publint doesn't catch this.
^4.0.0 works alongside the workspace link even though components/package.json says 1.0.6 (semantic-release sets the real version only at publish time): npm still resolves it to ./components, with no extra registry copy.
Merging this produced the first real release, @swr-data-lab/components-map@1.0.0 (tag components-map-v1.0.0), with the peer dependency in the published manifest.
What
Declare
@swr-data-lab/componentsas a peer dependency (^4.0.0) of@swr-data-lab/components-map. The"*"devDependency stays, for the workspace link.Why
19 modules in
components-map/distimport@swr-data-lab/components, but it was only listed as a devDependency. Installingcomponents-mapon its own left those imports unresolved. publint doesn't catch this.^4.0.0works alongside the workspace link even thoughcomponents/package.jsonsays1.0.6(semantic-release sets the real version only at publish time): npm still resolves it to./components, with no extra registry copy.Merging this produced the first real release,
@swr-data-lab/components-map@1.0.0(tagcomponents-map-v1.0.0), with the peer dependency in the published manifest.