Export 'default' not found in 'backbone' (module has no exports)
Yes, I'm able to reproduce it on grapesjs-style-filter too, same types of errors.
Read full answer below ↓Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Firefox 109
Reproducible demo link
none
Describe the bug
How to reproduce the bug?
(clone repo)
$ yarn
$ yarn start
What is the expected behavior?
The development server starts.
What is the current behavior?
yarn run v1.22.18
$ run-p start:*
$ npm run build:css -- --watch
$ grapesjs-cli serve
> [email protected] build:css
> sass src/styles/scss/main.scss dist/css/grapes.min.css --no-source-map --style=compressed --load-path=node_modules --watch
Start the development server...
Sass is watching for changes. Press Ctrl-C to stop.
<i> [webpack-dev-server] Project is running at:
<i> [webpack-dev-server] Loopback: http://localhost:8080/
<i> [webpack-dev-server] On Your Network (IPv4): http://10.10.0.235:8080/
<i> [webpack-dev-server] On Your Network (IPv6): http://[fe80::1]:8080/
<i> [webpack-dev-server] Content not from webpack is served from '/Users/mnutt/p/src/grapesjs' directory
<i> [webpack-dev-middleware] wait until bundle finished: /
asset grapes.min.js 3.15 MiB [emitted] (name: main)
asset index.html 3.92 KiB [emitted]
runtime modules 27.7 KiB 14 modules
orphan modules 465 bytes [orphan] 5 modules
modules by path ./src/ 1.5 MiB 245 modules
modules by path ./node_modules/ 926 KiB
modules by path ./node_modules/underscore/modules/*.js 83.5 KiB 161 modules
modules by path ./node_modules/@babel/runtime/ 9.01 KiB 25 modules
modules by path ./node_modules/grapesjs-cli/node_modules/ 177 KiB 20 modules
modules by path ./node_modules/codemirror/ 517 KiB
./node_modules/codemirror/lib/codemirror.js 417 KiB [built] [code generated]
+ 4 modules
modules by path ./node_modules/promise-polyfill/src/*.js 7.48 KiB
./node_modules/promise-polyfill/src/index.js 5.84 KiB [built] [code generated]
+ 2 modules
+ 5 modules
WARNING in ./node_modules/grapesjs-cli/node_modules/webpack-dev-server/client/overlay.js 29:0-18
export 'default' (imported as 'ansiHTML') was not found in 'ansi-html-community' (module has no exports)
@ ./node_modules/grapesjs-cli/node_modules/webpack-dev-server/client/index.js?protocol=ws%3A&hostname=0.0.0.0&port=8080&pathname=%2Fws&logging=info&reconnect=10 9:0-57 107:6-10 165:6-10 174:6-10 205:27-40 222:6-10 239:28-41 256:6-10 270:6-10
WARNING in ./node_modules/grapesjs-cli/node_modules/webpack-dev-server/client/overlay.js 199:17-25
export 'default' (imported as 'ansiHTML') was not found in 'ansi-html-community' (module has no exports)
@ ./node_modules/grapesjs-cli/node_modules/webpack-dev-server/client/index.js?protocol=ws%3A&hostname=0.0.0.0&port=8080&pathname=%2Fws&logging=info&reconnect=10 9:0-57 107:6-10 165:6-10 174:6-10 205:27-40 222:6-10 239:28-41 256:6-10 270:6-10
<snip, lots of other errors like this>
ERROR in ./node_modules/@babel/runtime/regenerator/index.js 1:0
Module parse failed: 'import' and 'export' may appear only with 'sourceType: module' (1:0)
File was processed with these loaders:
* ./node_modules/grapesjs-cli/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
> import _typeof from "@babel/runtime/helpers/typeof";
|
| // TODO(Babel 8): Remove this file.
@ ./src/dom_components/view/ComponentTextView.js 13:0-61 104:54-78 109:15-39 185:60-84 193:15-39
@ ./src/dom_components/index.ts 131:0-57 235:22-39
@ ./src/editor/model/Editor.ts 110:4-29
@ ./src/editor/index.ts 59:0-41 80:22-33
@ ./src/index.js 9:0-30 57:21-27
webpack 5.73.0 compiled with 1 error and 44 warnings in 7381 ms
I'm using node v16.18.1 (MacOS) although had the same result on node 14 and node 18. Is there something obvious I'm doing wrong?
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (4)
Yes, I'm able to reproduce it on grapesjs-style-filter too, same types of errors.
I was able to circumvent this error by changing the build pipeline to output more modern javascript (via --targets="> 3%"), though that produces backbone errors due to the use of es6 classes.
I'm not able to reproduce on my side with a fresh install, are you using the dev branch?
Thanks for reporting this, @mnutt.
Security and dependency issues are important. The GrapesJS team actively works on keeping dependencies up-to-date.
For you right now:
- Run
npm audit fixto see available patches - Check for a newer GrapesJS version that may have already addressed this
- If available, test the latest stable release before upgrading
- If the vulnerability is critical,
npm audit fix --forceis an option, but test thoroughly
Understanding the risk:
- Review the specific vulnerability details on GitHub Security Advisories
- Not all high-severity issues affect your code path
- Some vulnerabilities only trigger under specific conditions
Staying current:
- Watch for new GrapesJS releases
- Subscribe to security notifications on the repo
- The team prioritizes security updates in their release cycle
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5154
TS2416: Property '_up' in type 'PropertyStack' is not assignable to the same property in base type 'PropertyComposite<PropertyStackProps>'
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? ---- Reproducible demo link https://codesa...
Issue #5923
GrapeJs not loading on browsers sometimes
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Firefox 126.0.1Reproducible demo link https:...
Issue #5742
Building on Windows 10+
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link N/A Des...
Issue #5274
Parser bug inside Remix
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v114 Reproducible demo link https:/...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.
Browse premium plugins →Related tutorials
In-depth guides on the same topic.
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Tutorial
GrapesJS vs Webflow vs Tilda: What to Choose for Your Business in 2026
Choosing the right website platform in 2026 is no longer just about building a site
Tutorial
GJS Market 2.0 - Donations, Tracking, Labels and Better Product Discovery
We’ve rolled out a new set of GrapesJS marketplace updates across GJS Market, focused on improving how creators distribute products
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.