Skip to content

[doc] Disable auto-included addon-docs when adding GFM plugin #31078

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

igorsantos07
Copy link

@igorsantos07 igorsantos07 commented Apr 6, 2025

Related to #24718 (could close it if I get some help haha), related to 24743

What I did

This fixes a confusing issue when you try to add the GFM plugin, when using addon-essentials (AFAIK, that's the default?): Storybook ignores the new plugin because the docs add-on was already included. Changing code order doesn't seem to help, either.

I only found the solution after digging through this old issue: #20091 (comment)

What's missing

This should also be fixed for v7, but I didn't find the correct branch to edit that - the "edit on GitHub" link simply takes me to next, where the v7 files don't exist anymore.

If someone can point me in the correct direct to fix that, I can also add a note about the requirement of remark-gfm@v3, as pointed at #24743 (comment) - this is also an issue I faced on v7. Then, I guess we could auto-close #24718.

Checklist for Contributors

Testing

This is just a documentation change, so no testing?

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

Updated the documentation snippet to clarify GFM plugin configuration with Storybook when using auto-included addon-docs from addon-essentials.

  • Updated docs/_snippets/storybook-main-config-remark-options.md to include clear JavaScript and TypeScript examples.
  • Added commented configuration instructions to disable addon-docs to prevent plugin conflicts.
  • Highlighted potential version issues with remark-gfm to aid user troubleshooting.

💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!

Actually, Greptile is incorrect on the version issues, as I don't mention version changes (yet) on the code changes.

This fixes a confusing issue when you try to add the GFM plugin, when using `addon-essentials` (AFAIK, that's the default?): Storybook ignores the new plugin because the `docs` add-on was already included. Changing code order doesn't seem to help, either.

I only found the solution after digging through this old issue: storybookjs#20091 (comment)

> **Note:** this should also be fixed for [v7](https://storybook.js.org/docs/7/writing-docs/mdx#anatomy-of-mdx), but I didn't find the correct branch to edit that - the "edit on GitHub" link simply takes me to `next`, where the v7 files don't exist anymore.
@igorsantos07 igorsantos07 marked this pull request as ready for review April 6, 2025 18:47
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

@valentinpalkovic
Copy link
Contributor

Hi @igorsantos07

Thank you very much for your contribution.

In Storybook 9, we eliminate @storybook/addon-essentials and merge all essential addons into Storybook's core instead, except @storybook/addon-docs. Therefore, I believe this PR is not relevant anymore. I will close it. Let me know, if you think otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Documentation]: Need instruction on how to get basic extended Markdown functionalities such as table
2 participants