Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webpack resolver fails on CircleCI #767

Closed
mattkrick opened this issue Mar 14, 2017 · 4 comments · Fixed by #768
Closed

webpack resolver fails on CircleCI #767

mattkrick opened this issue Mar 14, 2017 · 4 comments · Fixed by #768

Comments

@mattkrick
Copy link
Contributor

Everything works great locally, but I kick it up to CircleCI & I get a few thousand errors saying:

Resolve error: Cannot convert undefined or null to object

example (under npm run lint)
https://circleci.com/gh/ParabolInc/action/2142

my settings:

  "settings": {
    "import/parser": "babel-eslint",
    "import/resolver": {
      "webpack": {
        "config": "./webpack/prod.babel.js" // points to a file that babelifies my webpack config
      }
    },
  },
mattkrick added a commit to mattkrick/eslint-plugin-import that referenced this issue Mar 14, 2017
is not the root cause of import-js#767, but it at least makes it possible for folks to figure out real fast what is causing the error.
fix import-js#767
@markphilpot
Copy link

@mattkrick I just hit this exact error in CircleCI... what did you do to fix it?

@mattkrick
Copy link
Contributor Author

Oh dang, I don't remember. My project is all open source though so you can check out the commit log.

If you run my fork it'll show the error and that should point you in the right direction.

@warreng
Copy link

warreng commented Oct 24, 2017

@mattkrick did you find a solution for this? It looks as though the rules related to imports were just switched off in this case see https://github.com/ParabolInc/action/pull/810/files

@mattkrick
Copy link
Contributor Author

for me, the problem was in the application, but this module wasn't giving me the right error. My PR fixes that & provides the correct error so you can properly diagnose your app.

ljharb pushed a commit to mattkrick/eslint-plugin-import that referenced this issue Jun 15, 2018
is not the root cause of import-js#767, but it at least makes it possible for folks to figure out real fast what is causing the error.
fix import-js#767
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants