Skip to content

Support circular dependencies and export let with experimentalImportSupport#1429

Open
robhogan wants to merge 1 commit intomainfrom
export-D68394514
Open

Support circular dependencies and export let with experimentalImportSupport#1429
robhogan wants to merge 1 commit intomainfrom
export-D68394514

Conversation

@robhogan
Copy link
Contributor

@robhogan robhogan commented Jan 19, 2025

Summary:
Currently, experimentalImportSupport transforms named imports such that they're accessed immediately at the top level, eg:

import {foo} from 'bar';
export function getFoo() {
  return foo;
}

Becomes

Object.defineProperty(exports, '__esModule', {
  value: true
});
var foo = require('bar').foo;
function getFoo() {
  return foo;
}
exports.getFoo = getFoo;

This immediate, top-level assignment of require('bar').foo to foo is problematic for two reasons:

  1. In the case of circular dependencies, the module at 'bar' may not have been fully initialised, so that foo might be undefined at this point.
  2. In the case where bar defines export let foo = 'something mutable', a reassigment of foo within 'bar' at runtime will not be reflected by the importing module.

Differential Revision: D68394514

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jan 19, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D68394514

facebook-github-bot pushed a commit that referenced this pull request Jan 20, 2025
Summary:

Currently, `experimentalImportSupport` transforms named imports such that they're accessed immediately at the top level, eg:

```js
import {foo} from 'bar';
export function getFoo() {
  return foo;
}
```

Becomes
```js
Object.defineProperty(exports, '__esModule', {
  value: true
});
var foo = require('bar').foo;
function getFoo() {
  return foo;
}
exports.getFoo = getFoo;
```

This immediate, top-level assignment of `require('bar').foo` to `foo` problematic for two reasons:
1. In the case of circular dependencies, the module at `'bar'` may not have been fully initialised, so that `foo` might be undefined at this point.
2. In the case where `bar` defines `export let foo = 'something mutable'`, a reassigment of `foo` within `'bar'` at runtime will not be reflected by the importing module.

Differential Revision: D68394514
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D68394514

Summary:

NOTE: This is an opt-in extension to `experimentalImportSupport`, this diff is a no-op by default.

Currently, `experimentalImportSupport` transforms named imports such that they're accessed immediately at the top level, eg:

```js
import {foo} from 'bar';
export function getFoo() {
  return foo;
}
```

Becomes
```js
Object.defineProperty(exports, '__esModule', {
  value: true
});
var foo = require('bar').foo;
function getFoo() {
  return foo;
}
exports.getFoo = getFoo;
```

This immediate, top-level assignment of `require('bar').foo` to `foo` problematic for two reasons:
1. In the case of circular dependencies, the module at `'bar'` may not have been fully initialised, so that `foo` might be undefined at this point.
2. In the case where `bar` defines `export let foo = 'something mutable'`, a reassignment of `foo` within `'bar'` at runtime will not be reflected by the importing module.

This aims to fix 1 and get closer to a fix for 2. The new output would be:

```js
Object.defineProperty(exports, '__esModule', {
  value: true
});
var _bar = require('bar');
function getFoo() {
  return _bar.foo;
}
exports.getFoo = getFoo;
```

By lazily accessing values

Differential Revision: D68394514
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D68394514

@thespacemanatee
Copy link

Hey @robhogan, I wanted to say thanks for this fix and ask if anything is blocking this from merging. My team wants to try the React Compiler on our Expo project, and this is the current blocker for that. Thanks again!

@dannyhw
Copy link

dannyhw commented Jul 22, 2025

Hey just wondering if there's any update? With storybook we're seeing issues with enabling the react compiler that seem like they could be related to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants