Non-named plugins and options

This seems to be related to https://github.com/microsoft/TypeScript/issues/35945 As a workaround you could do something like this for now:

pluginsOpts: {
  [myPlugin.toString()]: {
     customField: 'customValue'
  }
}

I guess for the TS type safety we would need to introduce some kind of helper for plugins

import grapesjs, { usePlugin } from 'grapesjs';
import somePlugin from 'gjs-plugin';

grapesjs.init({
  // ...
  plugins: [
    // no need for `pluginsOpts`
    usePlugin(somePlugin, { option1: 'A', option2: 'B', ... })
  ]
});

that sounds to be a good idea

Added the helper here (I'll also update the docs with the usage later)

Thanks for reporting this, @jchautreux.

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