Why there is a Unknown tag around story source

Describe the bug There is a Unknow tag around story source

To Reproduce Steps to reproduce the behavior:

1. Go to ‘…’
2. Click on ‘…’
3. Scroll down to ‘…’
4. See error

Expected behavior There is not a Unknow tag aroud story source

Screenshots

Code snippets

// .storybook/addons.js
import "storybook-addon-jsx/register";
import "@storybook/addon-knobs/register";

// .storybook/config.js
import { addDecorator, configure } from "@storybook/react";

import { Fragment } from "react";
import { jsxDecorator } from "storybook-addon-jsx";
import { withInfo } from "@storybook/addon-info";
import { withKnobs } from "@storybook/addon-knobs";

addDecorator(jsxDecorator);
addDecorator(withKnobs);
addDecorator(withInfo({ inline: true, propTablesExclude: [Fragment] }));

function loadStories() {
  require("../stories/index.js");
}

configure(loadStories, module);

import React, { Fragment } from "react";

import { Button } from "@cp/ec-ui";
import { storiesOf } from "@storybook/react";

// import { boolean, text } from "@storybook/addon-knobs";

storiesOf("Button", module)
  .add("type prop", () => (
    <div>
      <Button type="primary">Primary Button</Button>
      <Button type="danger">Danger Button</Button>
      <Button>Normal Button</Button>
    </div>
  ))
  .add("with emoji", () => (
    <Button>
      <span role="img" aria-label="so cool">
        😀 😎 👍 💯
      </span>
    </Button>
  ));

System:

• OS: Windows10
• Device: PC
• Browser: chrome, safari
• Framework: react
• Addons: storybook-addon-jsx、@storybook/addon-info、@storybook/addon-knobs
• Version: 5.0.11

Additional context Add any other context about the problem here.

[shilman]

FYI addon-info is being superceded by addon-docs, which fixes a bunch of bugs and is easier to maintain. It’s reached release candidate (RC) status and will be properly released soon. Please give it a try! https://medium.com/storybookjs/storybook-docspage-e185bc3622bf

[stale[bot]]

Hey there, it’s me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!