Aviad Moreshet

+1 I also suffer from this and nothing works. Have to reload server on every new file. :/

Downgrading `react-dev-utils` didn't help. Really need 3.0.0 because older versions of `jest` has bugs.

Any fix? Still receiving this error today and it's very annoying.

Not working yet... have you published it to npm?

And another issue. I'm using 1.3.4 now. Cannot reach the swagger UI. The /docs route works well, but when I access the app in it's default port e.g. http://localhost:3000 then...

Yeah but I want to be able to serve the UI by myself and not depend on external swagger.io. Do you have any explanations why it's not working? Maybe I...

No I haven't... why would I run from source code? :P I want to consume the module just as normal node module via npm installing. By the way, is app.js...

Would swagger-ui work in that way? Because I've just made a service of mine that serves the swagger-ui, and now instead to serve the /docs JSON from the same service...

@songguanglu Do you have somewhere the implementation of TSD on RetinaNet you've done, for reference?

A temporary solution (until they fix their bug) would be to specifically inject the 'falsy' value during the install/upgrade phase via flag.