Module not found: Error: Can't resolve 'utils/mixins'

You shouldn't try to compile grapesjs source code as the source could contain bundler-related content (as the one you mention, it's not an external package)

@artf you shouldn't try to close tickets without reading them first.

If you will read the issue, you will see that i mentioned when i "updated" it, i updated it using npm i by changing grapesjs version in package.json to latest version.

The code breaks from 0.19.4 onwards, since you started using .ts file in modules.ts

Yeah I understand that you have simply updated the version but it looks like you're trying to read the source of the grapesjs package, which is wrong (probably in the future, the src folder will be even removed)

Thanks for reporting this, @nabtron.

Security and dependency issues are important. The GrapesJS team actively works on keeping dependencies up-to-date.

For you right now:

1. Run npm audit fix to see available patches
2. Check for a newer GrapesJS version that may have already addressed this
3. If available, test the latest stable release before upgrading
4. If the vulnerability is critical, npm audit fix --force is 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