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
- [New] add missing core modules, and determine them dynamically by node version
- [Fix] `resolve.sync` should re-throw non `ENOENT errors (#79)
- [Fix] Create error outside process.nextTick (#103)
- [Dev Deps] update `tape`; add `safe-publish-latest`
- [Tests] test on every minor version of node
https://github.com/substack/node-resolve/blob/1.1.6/lib/sync.js#L9-L11
It is possible for
fs.statSync
to fail do for reasons other then ENOENT. As such, we should re-throw or we end up with an un-related error do to the stat object being missing: https://github.com/substack/node-resolve/blob/1.1.6/lib/sync.js#L1note this would also fix the a-symmetry with async – which correctly handles the error https://github.com/substack/node-resolve/blob/1.1.6/lib/async.js#L23
an example would be:
fs.statSync('\\\\some-unc-path\\folder name\\missing file')
will throw unfortunately throw anUnknownError
:(The text was updated successfully, but these errors were encountered: