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
I think the change in #922 broke the importing of copySync in ESM mode a bit. The error is below
import { mkdirs, copySync } from 'fs-extra';
^^^^^^^^
SyntaxError: Named export 'copySync' not found. The requested module 'fs-extra' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from 'fs-extra';
const { mkdirs, copySync } = pkg;
This did not happen in 10.0.0.
Operating System: macOS 11.6.4
Node.js version: 16.8.0
fs-extra version: 10.0.1
The text was updated successfully, but these errors were encountered:
@RyanZim Reading #746 and it seems like I was lucky to be able to use fs-extra in this ESM-like fashion so far... Let me know what you think, I'm happy to close this if you confirm this is totally by accident and we should avoid using this ESM-like approach till #746 is resolved. Thanks!
I think the change in #922 broke the importing of
copySync
in ESM mode a bit. The error is belowThis did not happen in
10.0.0
.fs-extra
version: 10.0.1The text was updated successfully, but these errors were encountered: