Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Flow: Property not found

See original GitHub issue

After an update I have this issue. I check my code func children is there

220:             <Motion 
                 ^ React element `Motion`
 22:   propTypes: {
       ^^^^^^^^^ property `children`. Property not found in. See: ../node_modules/react-motion/lib/Motion.js.flow:22
220:             <Motion 
                 ^ props of React element `Motion`

Issue Analytics

State:
Created 7 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

6reactions

cdebottoncommented, Apr 3, 2017

Any progress on merging this? Would love to see this resolved as we’re relying heavily on flow and this pollutes the actual flow report.

0reactions

AugustinLFcommented, Aug 23, 2017

This is fixed with Flow 0.53. However, flow detects errors in react-motion, due to how the React types evolved 😕

Top Results From Across the Web

Flow - Property not found in statics of class - Stack Overflow

One solution would be to not make it at static at all and just have it be a variable in the file. –...

do property not found in object literal errors really help anyone?

We can work around this issue by always constructing an empty object literal and adding properties to it. See here for more: facebook/flow#1606 ......

Object Types - JavaScript. Flow

Unsealed objects allow new properties to be written at any time. Flow ensures that reads are compatible with writes, but does not ensure...

New Flow Errors on Unknown Property Access in Conditionals

TL;DR: Starting in 0.68.0, Flow will now error when you access unknown properties in conditionals. Flow already disallows accessing unknown ...

No suggestions to autocomplete missing properties in Flow by ...

Currently, when you create an empty object {} of an expected type X = {a: string, b: number} , there is no autocompletion...