Error on start story book

[guidiego]

I'm on OS X Yosemite 10.10.5, and when I start storybook I got this:

webpack built 358ded7c0213c865dc6d in 10316ms
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2017-02-23 09:32 node[67323] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)

[ndelangen]

😢 That doesn't look good. Could you provide more information?
Something so we could begin to try reproduce this issue?

What have you tried?
Do you have some repo we could take a look at?

[guidiego]

@ndelangen I forgot to say, but when I restart the Mac, the storybook work fine again. More info about Hardware/Software:

Mac 2011
System: OS X Yosemite (Version 10.10.5)
Processor: 2.5 GHz Inter Core i5
Memory: 8GB 1333MHz

[ndelangen]

If you or anyone experiences this problem again, please re-open this issue. 👍

[lavelle]

Just encountered this and a restart didn't fix it.

Seemed to happen after switching Node versions. I moved from nvm to using n. Still on the same node version though. 6.2.2. I tried removing node_modules and starting from scratch, no dice.

System: https://cl.ly/3u0S3c1u0710

[ndelangen]

Can you provide stuff like:

• node version
• npm version
• storybook version

I'm expecting you're using a very old version of node..

[ndelangen]

I hear a reboot may help ¯\_(ツ)_/¯

[lavelle]

I've tried rebooting iTerm and my machine, neither helped.

This has happened on Node v6, v7 and v8, with npm v3 and v6, and Yarn v0.27.

We're using the latest Storybook, v3.1.8, with the latest versions of our addons (actions, knobs and info)

This seems to be a webpack issue, I found lots of similar issues: https://www.google.co.uk/search?q=FSEventStreamStart%3A+register_with_server%3A+ERR&oq=FSEventStreamStart%3A+register_with_server%3A+ERR

This answer seemed the most hopeful: facebook/react-native#9309 (comment)

But I tried both increasing the file limit and installing Watchman and neither helped.

Maybe this issue should move to the webpack repo, but it seems like it's project specific, so maybe there is some storybook-specific fix.

In particular, right before I get the file error I get

> @thumbtack/thumbprint-react@0.0.0 server /Users/glavelle/Thumbtack/thumbprint-react
> start-storybook -p 9001 -c ./storybook

@storybook/react v3.1.8

=> Loading custom .babelrc
=> Loading custom addons config.
=> Loading custom webpack config (extending mode).
webpack built f1678ab60d02b8b03477 in 12010ms
Storybook started on => http://localhost:9001/

webpack building...
 10% building modules 0/1 modules 1 active ...mbprint-react/packages /stories\.js$/2017-07-11

And if I delete the line to load the stories files in my config.js, that goes away, so it appears to be something to do with the way storybook loads configs using webpack's require.context

Here's our full config.js for more info:

import { configure, setAddon } from '@storybook/react';
import { forEach } from 'lodash';
import infoAddon from '@storybook/addon-info';
import './demo.scss';

setAddon(infoAddon);

const req = require.context('../packages/', true, /stories\.js$/);

const loadStories = () => {
    forEach(req.keys(), req);
};

configure(loadStories, module);

[lavelle]

cc @danoc in case he's seen this

[ndelangen]

Can you try loading just a single story (instead of all via webpack.context)?
If the problem goes away,
Can you try loading just a single story but this time via webpack.context?
If the problem goes away,
Can you try adding your stories 1 by 1
At which point does the error return?
What's special about that story file?

[frehner]

I had a very similar issue as well.

I found jestjs/jest/issues/1767 and the solution there solved it for me. Solution:

Install/update Watchman using brew install watchman

[ndelangen]

Sounds like there's not much we can do on our side to help with this issue. Sounds like it's a variety of environment issues that are causing the same symptoms.