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

Unable to find a config file #149

Closed
jonataswalker opened this issue Jun 20, 2017 · 6 comments
Closed

Unable to find a config file #149

jonataswalker opened this issue Jun 20, 2017 · 6 comments

Comments

@jonataswalker
Copy link

  • nps version: 5.3.2
  • node version: 8.1.2
  • npm version: 5.0.3

Scripts file (or at least the relevant bits):

exports.scripts = {
  dev: {
    default: {
      script: concurrent.nps(
        'bundleDeps.browser.dev',
        'build.css.dev',
        'build.browser.dev',
        'build.server.dev',
        'server.dev'
      )
    }
}

package.json

{
  "scripts": {
    "start": "nps -c ./build/package-scripts.js"
  }
}

The command executed:

npm start dev

The output:

> nps -c ./build/package-scripts.js "dev"

nps is executing `dev`: node node_modules/concurrently/src/main.js --kill-others-on-fail --prefix-colors "bgBlue.bold,bgMagenta.bold,bgGreen.bold,bgBlack.bold,bgCyan.bold" --prefix "[{name}]" --names "bundleDeps.browser.dev,build.css.dev,build.browser.dev,build.server.dev,server.dev" 'nps bundleDeps.browser.dev' 'nps build.css.dev' 'nps build.browser.dev' 'nps build.server.dev' 'nps server.dev'
[build.browser.dev] Unable to find a config file and none was specified.

Suggested solution:

Gotta pass the same config file to all subsequent scripts?

@jonataswalker
Copy link
Author

ping @kentcdodds

@kentcdodds
Copy link
Collaborator

I'm on vacation. I'll get to it when I can. Thanks for your patience.

@RichDonnellan
Copy link

@jonataswalker Follow issue #139 and kentcdodds/nps-utils#13. Sounds like you're facing the same troubles. Hopefully, it will be resolved in an upcoming release.

@jonataswalker
Copy link
Author

Ah ok @RichDonnellan thank for pointing it.

@Miklet
Copy link
Collaborator

Miklet commented Jul 21, 2017

@jonataswalker Do you mind if I close this issue since there are two others you can track?

@kentcdodds
Copy link
Collaborator

Yeah, let's do that. Thanks @Miklet 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants