Flow: Error when importing relative paths

Created on 21 Jan 2019 · 11Comments · Source: facebook/flow

Issue Summary

When importing certain relative path modules I get the following error;

[Flow] Cannot resolve module `../<file name>`. [InferError]

The file paths that Flow has this error for do exist.

To Reproduce

├── src
│   └── index.js <--- `import * from '../lib/foo'`
├── lib
│   └── foo.js

Import a module from a different directory in a parent of files directory

I'm not 100% this isn't also caused in other local path patterns.

Further Information

Actual directory structure

|-cypress
|  | ... Cypress test files / folder ...
|-bin
|-gallery
|  |-components <--- `[Flow] Cannot resolve module `../lib/filename`. [InferError]`
|  |-data
|  |-docs
|  |-lib
|- node_modules
|  | ... all the modules ...
|-.github
|-lib
|  | ... built files ...
|-flow-typed
|  | ... flow typed modules ...
|-src
|  | ... main code ...

.flowconfig

[ignore]
.*/cypress/**/*
.*/lib/**/*
.*/node_modules/**/*
.*/docs/*

[include]

[libs]

[lints]

[options]
all=true

[strict]

Technical details:

Node Version: v9.11.2
OS: OS X 10.14

question

Source

matthojo

👍2

All 11 comments

What is your flowconfig and where do you keep it?

TrySound on 21 Jan 2019

@TrySound thanks for the quick response.

.flowconfig is in the root of the project.

This is what we have;

.flowconfig

[ignore]
.*/cypress/**/*
.*/lib/**/*
.*/node_modules/**/*
.*/docs/*

[include]

[libs]

[lints]

[options]
all=true

[strict]

matthojo on 21 Jan 2019

The problem could be that the lib folder is in your [ignore] section

0rvar on 21 Jan 2019

👍1

@0rvar Thank you, I _just_ updated my comment as you posted this 😁The example tree structure in my post was for illustrative purposes only and doesn't reflect my exact use-case. Let me see if I can create a more comprehensive version.

matthojo on 21 Jan 2019

Updated original post

I've added some additional information on the exact directory structure and config I'm seeing the error with.

matthojo on 21 Jan 2019

@matthojo You ignored lib and flow cannot resolve to it. That's the problem.

TrySound on 21 Jan 2019

👍1

@TrySound thanks, I’ll take a look in the morning - I _think_ this may also be happening for files outside of lib.
Out of interest does the ‘lib’ folder exclusion in the flow config traverse sub-directories? I was only intending it on being ‘lib’ in the project root.

matthojo on 21 Jan 2019

So, I've looked into this again and there are other modules from other areas outside of lib causing errors.

One example;

|-cypress
|  | ... Cypress test files / folder ...
|-bin
|-gallery
|  |-components
|  |  |-isolated <--- `[Flow] Cannot resolve module `../../../src/Filename`. [InferError]`
|  |-data
|  |-docs
|  |-lib
|- node_modules
|  | ... all the modules ...
|-.github
|-lib
|  | ... built files ...
|-flow-typed
|  | ... flow typed modules ...
|-src
|  | ... main code ...

matthojo on 22 Jan 2019

I have the exact same problem. I'm not ignoring any folder except stuff in node_modules.

It seems like flow is trying to resolve the module from the root folder of my project. e.g:

import { User } from '../../../models';

throws the following error:

Cannot resolve module /Users/20syl/Documents/models/index.js.

My folder architecture looks like this:

Users
 - 20syl
  - Documents
   - www
    - myApp
     - src
      - module
       - models
        index.js
       - components
        - MyComponent
         - SubComponent
          - index.js
        - MySecondComponent
         ... etc.

My app is very large and has tons of relative imports, which works well. For instance other files are importing the same file but work correctly.

Poirette on 19 Feb 2019

👍1

also having this issue. Actually it's just when using Webstorm...if i run the "flow" command, the errors don't show up. Also if i control click the reference in webstorm (with the "use webstorm to resolve files" option clicked) it will bring me to the folder...so it can clearly resolve it.