Issue #6570πŸ’¬ AnsweredOpened July 20, 2025by nanto0 reactions

Parser ignores `parser.optionsHtml.keepEmptyTextNodes` option

Quick answerby ClaudeCode

Thanks for reporting this, @nanto. Great question about parser ignores parser.optionsHtml.keepEmptyTextNodes option. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the on() event listener method Most operations c...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrom v140.0.7307.0 (canary)

Reproducible demo link

https://jsfiddle.net/y3gr69s4/

Describe the bug

How to reproduce the bug?

  1. Create editor instance with parser.optionsHtml.keepEmptyTextNodes option set true.
    const editor = grapesjs.init({
      parser: {
        optionsHtml: {
          keepEmptyTextNodes: true,
        },
      },
    });
    
  2. Load HTML code that contains newlines between elements.
    editor.setComponents('<body>\n<p>foo</p>\n<p>bar</p>\n</body>');
    
  3. Get HTML code.
    const result = editor.getHtml();
    

What is the expected behavior? The resulting HTML code still contains newlines between elements.

<body>
<p>foo</p>
<p>bar</p>
</body>

What is the current behavior? Newlines between elements are stripped from the resulting HTML code.

<body><p>foo</p><p>bar</p></body>

We get the expected result if we set parser.keepEmptyTextNodes option to true but it causes TypeScript type error. I think that keepEmptyTextNodes should be a property of optionsHtml since it is irrelevant to CSS parser.

const editor = grapesjs.init({
  parser: {
    // Error: 'keepEmptyTextNodes' does not exist on type 'ParserConfig'
    keepEmptyTextNodes: true,
  },
});

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (1)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @nanto.

Great question about parser ignores parser.optionsHtml.keepEmptyTextNodes option. The recommended approach with StyleManager is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

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.

All tutorials β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.