Circular dependencies warning when bundling the @datadog/browser-logs
See original GitHub issueI was using rollup to bundle my package that consumes @datadog/browser-logs
and get following error.
node_modules/@datadog/browser-core/esm/tools/utils.js -> node_modules/@datadog/browser-core/esm/domain/internalMonitoring.js -> node_modules/@datadog/browser-core/esm/tools/error.js -> node_modules/@datadog/browser-core/esm/tools/utils.js
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
How to Eliminate Circular Dependencies from Your JavaScript ...
While circular dependencies may not directly result in bugs, they will almost always have unintended consequences.
Read more >How to fix nasty circular dependency issues once and for all in ...
For example, in codesandbox, when bundling our app with Parcel (or Webpack or Rollup), this solution doesn't work. However, when running this ...
Read more >"Circular dependency detected" warning - Angular
This warning comes when you use code of one module in another and vice ... A. so in this scenario you will get...
Read more >How to Analyze Circular Dependencies in ES6? - Railsware
It is caused by circular dependencies that cannot be resolved synchronously by webpack. One is undefined, hence the error.
Read more >circular-dependency-plugin | Yarn - Package Manager
Detect modules with circular dependencies when bundling with webpack. Circular dependencies are often a necessity in complex software, the presence of a ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Are there any updates or solution to prevent this warning? I’m seeing this on build as of today
(!) Circular dependencies node_modules/@datadog/browser-core/esm/domain/internalMonitoring.js -> node_modules/@datadog/browser-core/esm/tools/error.js -> node_modules/@datadog/browser-core/esm/domain/internalMonitoring.js node_modules/@datadog/browser-core/esm/domain/internalMonitoring.js -> node_modules/@datadog/browser-core/esm/tools/error.js -> node_modules/@datadog/browser-core/esm/domain/tracekit/index.js -> node_modules/@datadog/browser-core/esm/domain/tracekit/computeStackTrace.js -> node_modules/@datadog/browser-core/esm/domain/tracekit/report.js -> node_modules/@datadog/browser-core/esm/domain/internalMonitoring.js node_modules/@datadog/browser-core/esm/domain/tracekit/computeStackTrace.js -> node_modules/@datadog/browser-core/esm/domain/tracekit/report.js -> node_modules/@datadog/browser-core/esm/domain/tracekit/computeStackTrace.js …and 6 more
Thanks for your feedback. We will experiment with shiping bundled NPM packages, so it should resolve the issue of circular dependencies. We’ll keep you up to date on this topic!