The services package depends on digitallink_toolkit_server via a local file: reference (file:../../digitallink_toolkit_server). This dependency is not published to npm, which means:
- The package cannot be consumed externally without subpath exports that bypass the main entry point
- Tests that transitively import from the main entry fail in any environment where the local directory doesn't exist
- It forces the published package to exclude it from dependencies entirely, creating a runtime mismatch between the workspace and the published artifact
Current Workaround
Subpath exports (./encryption, ./key-provider) let external consumers avoid the main entry point. The barrel files document this with a Remove once digitallink_toolkit_server is eliminated comment.
Expected Outcome
Replace digitallink_toolkit_server with a published npm package or inline the required functionality, so the main entry point works without local file dependencies.
Affected Files
packages/services/package.json (the file: dependency)
packages/services/src/linkResolver.service.ts (imports from it)
packages/services/src/identityProviders/GS1Provider.ts (imports from it)
The services package depends on
digitallink_toolkit_servervia a localfile:reference (file:../../digitallink_toolkit_server). This dependency is not published to npm, which means:Current Workaround
Subpath exports (
./encryption,./key-provider) let external consumers avoid the main entry point. The barrel files document this with aRemove once digitallink_toolkit_server is eliminatedcomment.Expected Outcome
Replace
digitallink_toolkit_serverwith a published npm package or inline the required functionality, so the main entry point works without local file dependencies.Affected Files
packages/services/package.json(thefile:dependency)packages/services/src/linkResolver.service.ts(imports from it)packages/services/src/identityProviders/GS1Provider.ts(imports from it)