Issue updating @bynder/compact-view to v5 - Missing dependencies

Thank you for taking the time to ask your question ​@Aleksandr! I believe it would be best for Support to look into this further. You can find out how to submit a support ticket here or I am happy to do so on your behalf if you can share who the Account is.

Same for me.

This issue where your bundler reports "Could not resolve" certain dependencies after updating the @bynder/compact-view package is likely due to those dependencies not being available in the public npm registry.

The missing dependencies you might be seeing (based on common issues with this package) are:

• @bynder/design-system
• @bynder/icons
• @bynder/dat-frontend

These packages are internal Bynder components and are not typically published to the public npm registry for third-party use.

Possible recommendations
The proper way to use the Bynder Universal Compact View depends on how it's intended to be integrated, which is usually either by including a JavaScript bundle directly (preferred for most integrations) or by configuring your build process to access a private registry.

1. Check for a Publicly Available Bundle (Recommended)
The most straightforward solution is often to use the pre-built JavaScript file provided by Bynder, which includes all necessary dependencies.

• Consult the Bynder documentation for the specific version you are trying to use. They usually provide a direct link to a hosted or bundled JavaScript file (e.g., a .js file or a CDN link) that you can load directly into your HTML. This completely bypasses the npm dependency resolution in your bundler.

2. Configure a Private Registry
If your project is authorized to build the application and you're meant to consume these internal packages via npm, you'll need to configure access to Bynder's private npm registry.

Contact Bynder Support to get the necessary credentials and the URL for their private npm registry.

• You will typically need to configure this registry in your project's .npmrc file using the following format:

@bynder:registry=https://your-bynder-private-registry.com/ //your-bynder-private-registry.com/:_authToken=YOUR_AUTH_TOKEN

• Replace the registry URL and YOUR_AUTH_TOKEN with the information provided by Bynder. Once configured, running npm install should be able to resolve and download the internal packages.

3. Temporarily Skip Peer Dependency Checks
In some cases, if the missing packages are listed as peer dependencies that are expected to be available only in a specific environment and you're sure they won't break your build, you can try forcing the installation. Use this with caution, as it can lead to a broken build or runtime errors.

• Run your installation command with the --legacy-peer-deps or --force flag:
• Bash
• npm install @bynder/compact-view --legacy-peer-deps
• # OR
• npm install @bynder/compact-view --force

For the Bynder packages specifically, the first solution (using the pre-built bundle) or the second (configuring the private registry) are the most likely and correct fixes.

There are multiple ways of installing so perhaps the client could also attempt a different method of installing: "To setup the Universal Compact View in your web app via the Cloudfront distribution, add the following line to your page: "

<script src="https://ucv.bynder.com/5.0.5/modules/compactview/bynder-compactview-5-latest.js"></script>

I have an update here ​@Aleksandr ​@mosoket992 the authentication token (In Step 2. Configure a Private Registry) you need can be retrieved using the OAuth App steps in the portal.