You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 4, 2021. It is now read-only.
If you pass preserveSymlinks: false to rollup-plugin-node-resolve, and your node_modules directory's contents are symlinked, then the namedExports config key doesn't work properly. This plugin creates a map with keys containing symlinked paths, whereas rollup asks it about real paths.
I found this because resolve 1.11.1 had a bug in its preserveSymlinks: false behavior where it would not realpath some symlinks. With that fixed in 1.12.0, namedExports stopped working.
I'm happy to write up a PR for fixing this if needed. Maybe can realpath the result of resolve and map that as well.
The text was updated successfully, but these errors were encountered:
* Support preserveSymlinks: false (fixes#400)
* remove only
* Promise.prototype.finally is too new
* Only realpath existing paths
* Update appveyor to ensure symlinks are enabled
mikeharder
added a commit
to Azure/azure-sdk-for-js
that referenced
this issue
Aug 7, 2019
- Update transitive dependency resolve to 1.12.0
- Fixes issue with symlink resolution which required dedupe workaround
- browserify/resolve#196
- Depends on [email protected]
- Supports preserveSymlinks:false
- rollup/rollup-plugin-commonjs#400
- Move buffer to full dependency of service-bus
- Packages required for browser bundles should be full dependencies
- Improves customer experience when generating bundles from our packages
- Add dependencies buffer and process to event-hubs
- Required to generate browser bundle
- Fixes#3326
If you pass preserveSymlinks: false to rollup-plugin-node-resolve, and your node_modules directory's contents are symlinked, then the namedExports config key doesn't work properly. This plugin creates a map with keys containing symlinked paths, whereas rollup asks it about real paths.
I found this because resolve 1.11.1 had a bug in its preserveSymlinks: false behavior where it would not realpath some symlinks. With that fixed in 1.12.0, namedExports stopped working.
I'm happy to write up a PR for fixing this if needed. Maybe can realpath the result of resolve and map that as well.
The text was updated successfully, but these errors were encountered: