question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error [ERR_PACKAGE_PATH_NOT_EXPORTED] when using rxjs v7

See original GitHub issue

Describe the bug It seems that rxjs version 7 breaks something inside marble.

To Reproduce

yarn add @marblejs/core fp-ts rxjs

Run the example as shown on the website

Desktop (please complete the following information):

  • MacOS 11.3
  • Node 16.0

The following error is thrown:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath ‘./internal/scheduler/AsyncScheduler’ is not defined by “exports” in ‘node_modules/rxjs/package.json’

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
JozefFlakuscommented, May 10, 2021

In order to have a compatibility with latest RxJS release we have to bump the framework to the next major version - 4.0. Please confirm my thoughts.

1reaction
JozefFlakuscommented, Sep 22, 2021

Closing because RxJS v7 support is added in the v4.0 release candidate.

Read more comments on GitHub >

github_iconTop Results From Across the Web

49 - Stack Overflow
js') throws an ERR_PACKAGE_PATH_NOT_EXPORTED error. This encapsulation of exports provides more reliable guarantees about package interfaces for ...
Read more >
package.json is not defined by "exports" - You.com
I was receiving Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath '. ... is not defined by "exports" when upgrading from v7.0.3 to v8.0.0 ... Error ...
Read more >
rxjs | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >
No "exports" main defined - Laracasts
resources/js/app.js Module build failed (from ./node_modules/babel-loader/lib/index.js): Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No &
Read more >
No "exports" main resolved in [#3118274] | Drupal.org
With Drupal 10 expected to launch on 14 December, ... Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main resolved in.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found