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
After running 'npm run dev', 'npm run watch' or 'npm run bundle', we're getting the following rebuilding warnings/errors:
Rebuilding...
(node:30073) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use node --trace-warnings ... to show where the warning was created)
Rebuilding...
(node:30177) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use node --trace-warnings ... to show where the warning was created)
Rebuilding...
(node:30173) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use node --trace-warnings ... to show where the warning was created)
The text was updated successfully, but these errors were encountered:
Are you getting these errors from a freshly generated theme, or have you modified it? Are you able to provide a copy of your repository? (I haven't seen these errors to date.)
Since this issue hasn't reached an active LTS version of Node.js, and since it's related to a third-party plugin, I'm going to close this for now. Please feel free to reopen if you encounter any further issues!
After running 'npm run dev', 'npm run watch' or 'npm run bundle', we're getting the following rebuilding warnings/errors:
Rebuilding...
(node:30073) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use
node --trace-warnings ...
to show where the warning was created)Rebuilding...
(node:30177) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use
node --trace-warnings ...
to show where the warning was created)Rebuilding...
(node:30173) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use
node --trace-warnings ...
to show where the warning was created)The text was updated successfully, but these errors were encountered: