Error: import or require() statements can be added only by editing a Markdown

[davidpaley]

I'm trying to make an example of my component in the Markdown file (.md). The problem is when I try to import something inside this markdown file:

import { validateEmail } from '../../utils/validation';

initialState = {
  value: 'asdas',
}

function updateValue(name, value) {
  setState({ [name]: value });  
}

<Input
  placeholder="Name"
  value={value}
  type="text"
  required={true}
  name="value"
  onChangeFunction={updateValue}
  validations={[validateEmail]}
/>;

When I go to the component it says:
Error: import or require() statements can be added only by editing a Markdown example file: ../../utils/validation

I tried also with require but it didn't work.

versions:

• react-styleguidist": "^9.0.3"
• "react": "^16.7.0",

Example of my project:
https://github.com/aimementoring/blueprint
branch: feature/validations

To reproduce

• download the project and execute:
• yarn
• yarn deploy
• serve -s styleguide
• go to the input component.

[kopax]

I think this is the same as #1310, we are currently invistagating for the root cause but we couldn't find, let us know if you get why. To me, all the module aliases are not working within examples.

The one think we can import is react. Can you please confirm that you can't import dependencies listed in package.json dependencies ?

[davidpaley]

Yes, me too. I have the error if I try to import any of the package.json dependencies except for react.

[timsnadden]

Try deleting yarn.lock|package-lock.json and reinstalling. I'm not sure which dependency is causing the issue but this fixes it

[kopax]

@timsnadden I don´t know where you got this. I am a package maintainer and we allow the wider range of semver for our users, We want to see things break and we do not use lock file for that reason (except in app). The only thing it could have change on your side is that it upgraded version on your particular host. To me, I already have the latest version and this bug is still present. You´re advice won´t help.

[timsnadden]

@kopax For me the issue was resolved by removing yarn.lock and reinstalling. It's a hacky solution but can perhaps provide a clue to identify the root cause. I'm sorry it didn't resolve the issue for you

[kopax]

Ok, now I got it and you are right. Let's continue in #1278