Cannot read properties of undefined (reading 'replace') at formatPluginName

[Aoyimiyak]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Prerequisites

• I'm using the latest version of Docusaurus.
• I have tried the npm run clear or yarn clear command.
• I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
• I have tried creating a repro with https://new.docusaurus.io.
• I have read the console error message carefully (if applicable).

Description

I report this error when I start the project

Reproducible demo

No response

Steps to reproduce

I updated the version to 3.4.0 and then started the project, and the terminal reported this error

Expected behavior

The project can be started normally

Actual behavior

1

Your environment

• Public source code:
• Public site URL:
• Docusaurus version used:
• Environment name and version (e.g. Chrome 89, Node.js 16.4):
• Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

• I'd be willing to fix this bug myself.

[OzakIOne]

Can you create a minimal repro ? There shouldn't be any issue upgrading docusaurus version, this might come from your setup

[slorber]

Please try again, this might be a temporary issue we had recently.

Until a runnable repro is provided (using https://docusaurus.new/stackblitz or GitHub), I'm going to close

[htmlin]

I've written a custom plugin that returns null under certain circumstances, and that's causing this issue. I hope this is helpful for you.

[slorber]

I've written a custom plugin that returns null under certain circumstances, and that's causing this issue. I hope this is helpful for you.

Curious to know more about this use-case

Maybe we could allow that

[slorber]

Forgot to mention but this original issue is related to #10239

We need plugins to have a name

But we could also allow a plugin to return null eventually, as a convenient way to self-disable depending on options 🤷‍♂️ can you explain that need @htmlin ?

Even if we allow this, this would only be a "shortcut" because you could also decide from the config file to filter out the plugin from the plugins array depending on context.

[slorber]

Note that we even have a use-case for this internally:
https://github.com/facebook/docusaurus/blob/main/packages/docusaurus-plugin-sitemap/src/index.ts#L21

So let's add the ability to return null!

[htmlin]

Forgot to mention but this original issue is related to #10239

We need plugins to have a name

But we could also allow a plugin to return null eventually, as a convenient way to self-disable depending on options 🤷‍♂️ can you explain that need @htmlin ?

Even if we allow this, this would only be a "shortcut" because you could also decide from the config file to filter out the plugin from the plugins array depending on context.

If I return a null value in the custom plugin, Docusaurus throws this error. So now, I’ve moved the condition check to the plugins configuration to bypass this issue.

[slorber]

This will be supported soon (v3.5)

PR: #10286