Building on Windows 10+
Yeah, I did all the usual stuff. Lock files, updates, various ways of imports ({}, require, *, full path, etc.) Not sure why, but when I break stuff, I break it good. Always tier 2 or 3 support LMAO. I do believe the issue resides in CLI, or... in conjunction with backbone-undo. Maybe path related, or symlinks, or......
Read full answer below βQuestion
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Chrome v122
Reproducible demo link
N/A
Describe the bug
How to reproduce the bug?
- Checkout git onto a Windows 10+ machine
- Build using provided procedure.
What is the expected behavior? It should build the same as in a *inx system.
What is the current behavior? The build fails with errors referencing Backbone:
WARNING in ./src/common/index.ts 35:2-16
export 'default' (imported as 'Backbone') was not found in 'backbone' (module has no exports)
@ ./src/editor/view/EditorView.ts 16:0-39 45:21-22 68:2-6
@ ./src/editor/index.ts 60:0-43 866:30-40
@ ./src/index.ts 13:0-30 61:25-31
WARNING in ./src/common/index.ts 43:2-21
export 'default' (imported as 'Backbone') was not found in 'backbone' (module has no exports)
@ ./src/editor/view/EditorView.ts 16:0-39 45:21-22 68:2-6
@ ./src/editor/index.ts 60:0-43 866:30-40
@ ./src/index.ts 13:0-30 61:25-31
WARNING in ./src/common/index.ts 51:2-15
export 'default' (imported as 'Backbone') was not found in 'backbone' (module has no exports)
@ ./src/editor/view/EditorView.ts 16:0-39 45:21-22 68:2-6
@ ./src/editor/index.ts 60:0-43 866:30-40
@ ./src/index.ts 13:0-30 61:25-31
WARNING in ./src/dom_components/model/Component.ts 1597:18-45
export 'Model' (imported as 'Model') was not found in 'backbone' (module has no exports)
@ ./src/dom_components/index.ts 97:0-74 262:23-32 267:26-35 588:30-39 588:41-56
@ ./src/editor/model/Editor.ts 91:0-52 138:4-20
@ ./src/editor/index.ts 59:0-41 79:22-33
@ ./src/index.ts 13:0-30 61:25-31
WARNING in ./src/dom_components/model/Component.ts 1625:25-53
export 'Model' (imported as 'Model') was not found in 'backbone' (module has no exports)
@ ./src/dom_components/index.ts 97:0-74 262:23-32 267:26-35 588:30-39 588:41-56
@ ./src/editor/model/Editor.ts 91:0-52 138:4-20
@ ./src/editor/index.ts 59:0-41 79:22-33
@ ./src/index.ts 13:0-30 61:25-31
WARNING in ./src/editor/model/Editor.ts 113:0-10
export 'default' (imported as 'Backbone') was not found in 'backbone' (module has no exports)
@ ./src/editor/index.ts 59:0-41 79:22-33
@ ./src/index.ts 13:0-30 61:25-31
WARNING in ./src/undo_manager/index.ts 76:23-34
export 'default' (imported as 'UndoManager') was not found in 'backbone-undo' (module has no exports)
@ ./src/editor/model/Editor.ts 108:0-51 118:4-21
@ ./src/editor/index.ts 59:0-41 79:22-33
@ ./src/index.ts 13:0-30 61:25-31
Environment:
Windows Server 2022 (fresh image)
VS Code 1.87.1 (latest)
Node v21.4.0 (latest)
All npm updates applied
This 'may' be related to GrapesJS CLI, I am not sure, as changes to the webpack.config.js, tsconfig.json seem to have no effect.
I have also tried building it directly, and it seems the Backbone may be having an issue using cash-dom instead of jquery.
Hitting a wall on this one.
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (4)
Yeah, I did all the usual stuff. Lock files, updates, various ways of imports ({}, require, *, full path, etc.)
Not sure why, but when I break stuff, I break it good. Always tier 2 or 3 support LMAO.
I do believe the issue resides in CLI, or... in conjunction with backbone-undo. Maybe path related, or symlinks, or... Β―_(γ)_/Β―
Anyway, I get the 'time' element. I burned too much time on it already, let me know if you get the itch lol
Good points. I have not tried the other versions of Node. I will give that a shot.
Yeah build/serve are managed by the CLI (let's move the issue there) but I'm not sure what might be the problem (no Windows to test π₯²)
Thanks for reporting this, @bernesto.
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 #4854
export 'default' not found in 'backbone' (module has no exports)
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 109 Reproducible demo link none De...
Issue #6087
Undo doesn't work after a Component's innerHTML is changed
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Latest Reproducible demo link https://jsfi...
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 #5631
Undo manager add() not working as expected
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v91 Reproducible demo link -- Descr...
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
How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services
A complete walkthrough of building a production GrapesJS editor: how to choose a preset, pick plugins, and scope setup services without burning a sprint.
Tutorial
GrapesJS Inline RTE Plugins Update: CKEditor 5 v0.1.4 and Froala Inline Text Editor
CKEditor 5 Inline for GrapesJS v0.1.4 fixes Studio SDK toolbar clipping, iframe injection and link balloon bugs. Compare with Froala Inline β both $69.
Tutorial
Embed GrapesJS in Your SaaS: A Weekend Guide
Embed GrapesJS in your SaaS and ship a white-label page builder over a weekend. Honest tradeoffs, real code, and the plugins that close the UX gap.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.