BUG: Building on Windows 10+ about grapesjs HOT 6 CLOSED

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

from grapesjs.

Good points. I have not tried the other versions of Node. I will give that a shot.

from grapesjs.

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 🥲)

from grapesjs.

Okay, I was suspecting it was at the CLI as well. I added some debugging code to check the output of the webpack.config.js at runtime. I did find and correct some backslash vs. forward slash path issues in the generated output, but it didn't correct the original issue.

If I spin you up a Windows vm in AWS with everything you need, could you take a look? Maybe I am missing something.

from grapesjs.

If I spin you up a Windows vm in AWS with everything you need, could you take a look? Maybe I am missing something.

I'm not sure when I'll be able to find time to check it honestly so don't do it 😅

Anyway, did you try to install it with yarn --frozen-lockfile?

from grapesjs.

I'd say this is not path-related issue, otherwise, you'd get another error (eg. unable to load module).
Worth noting that export 'default' (imported as 'X') was not found in 'Y' in the context of backbone/backbone-undo is technically correct as those are UMD bundled, but Webpack should apply some kind of interoperability wrapper and make them work as es modules, so for some reason this thing breaks on Windows.

I'm wondering if it might be related to the node version?! Did you try with v16/v18?

from grapesjs.