An open API service indexing awesome lists of open source software.

https://github.com/bhallstein/rollup-plugin-commonjs-dynamicrequireroot-symlink-issue

Reproduction of @rollup/plugin-commonjs dynamicRequireRoot symlink issue
https://github.com/bhallstein/rollup-plugin-commonjs-dynamicrequireroot-symlink-issue

Last synced: 21 days ago
JSON representation

Reproduction of @rollup/plugin-commonjs dynamicRequireRoot symlink issue

Awesome Lists containing this project

README

          

## @rollup/plugin-commonjs dynamicRequireRoot issue reproduction

Issue found when using @rollup/plugin-commonjs with dynamicRequireTargets/dynamicRequireRoot and a symlinked app directory.

Outline of files in project:
```
/folder/my-app - contains the app to be compiled
/folder/my-app/my-app.js
/folder/my-app/package.json
/folder/my-app/node_modules

/build.sh
/package.json
/rollup.config.js
```

To build:
```sh
bash build.sj
```

During build, build.sh first creates a symlink `/my-app -> /folder/my-app`, then invokes rollup, which takes `/my-app/my-app.js` as the input file.

### Expected behaviour

The require root should be correctly identified as a valid parent of the compiled file(s).

Ideally this should occur regardless of whether the require root is expanded from its symlink form or not.

### Issue

To reproduce both cases, run `bash build.sh` with `dynamicRequireRoot` in rollup.config.js set to either of the example lines located there.

#### 1. dynamicRequireRoot: 'my-app/node_modules'

Here the require root is `my-app/node_modules`. Error produced:

_[!] (plugin commonjs--resolver) RollupError: "/Users/ben/Desktop/rollup-plugin-commonjs-dynamicrequireroot-symlink-issue/folder/my-app/node_modules/sequelize/lib/dialects/abstract/connection-manager.js" contains dynamic require statements but it is not within the current dynamicRequireRoot "/Users/ben/Desktop/rollup-plugin-commonjs-dynamicrequireroot-symlink-issue/my-app/node_modules". You should set dynamicRequireRoot to "/Users/ben/Desktop/rollup-plugin-commonjs-dynamicrequireroot-symlink-issue/folder/my-app/node_modules/sequelize/lib/dialects/abstract" or one of its parent directories._

- The error is saying that the file's path is `folder/my-app/node_modules/sequelize/lib/dialects/abstract/connection-manager.js` — i.e. the file path is fully expanded from the symlink.
- It complains that `my-app/node_modules` is not a parent of `my-app/node_modules/.../.js`.
- It suggests setting the require root to `folder/my-app/node_modules` instead, as this would be a valid parent of the file path as stated.

#### 2. dynamicRequireRoot: realpathSync('my-app') + '/node_modules'

Here the require root is `folder/my-app/node_modules` — the expanded form as asked for in the above error. Error produced:

_[!] (plugin commonjs) RollupError: "/Users/ben/Desktop/rollup-plugin-commonjs-dynamicrequireroot-symlink-issue/my-app/node_modules/sequelize/lib/dialects/abstract/connection-manager.js" contains dynamic require statements but it is not within the current dynamicRequireRoot "/Users/ben/Desktop/rollup-plugin-commonjs-dynamicrequireroot-symlink-issue/folder/my-app/node_modules". You should set dynamicRequireRoot to "/Users/ben/Desktop/rollup-plugin-commonjs-dynamicrequireroot-symlink-issue/my-app/node_modules/sequelize/lib/dialects/abstract" or one of its parent directories._
- i.e. it is now stating the file path as `my-app/node_modules/sequelize/lib/dialects/abstract/connection-manager.js` — i.e. the non-expanded form.
- Rollup now makes the opposite complaint, i.e. that `folder/my-app/node_modules` is not a parent of `my-app/node_modules/.../.js`

To summarise: It's a catch-22:

- dynamicRequireRoot non-expanded: rollup says `` is not a parent of ``.
- dynamicRequireRoot expanded: rollup says: `` is not a parent of ``.

i.e.: curiously, when dynamicRequireRoot changes between expanded/non-expanded, the file path is considered non-expanded/expanded (i.e. the opposite) which seems to creates a conflict whatever you do.