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

gulp is a devDependency, when it should be a regular or peerDependency #801

Closed
heikomat opened this issue Jan 8, 2018 · 1 comment
Closed

Comments

@heikomat
Copy link

heikomat commented Jan 8, 2018

I'm submitting a bug report

  • Library Version:
    0.30.1

Please tell us about your environment:

  • Operating System:
    OSX 10.12.6

  • Node Version:
    8.9.4

  • NPM Version:
    5.6.0

  • Browser:
    not important

  • Language:
    not important

  • Loader/bundler:
    not important

Current behavior:
when installing aurelia-cli, gulp is not installed alongside it, because it is listed in the devDependencies.
running commands like au build doesn't work in that environment, because they require gulp

  • What is the expected behavior?
    gulp should be a regular dependency, or at least a peerDependency, because it is required to run commands like au build, and not only for the development of the aurelia-cli.

  • What is the motivation / use case for changing the behavior?
    I have a specific postinstall-script that moves and links dependencies depenending on what is mentioned in the package.json of local modules. because of that, and because the aurelia-cli doesn't state gulp as a dependency, the aurelia-cli ends up using a gulp-version of a different local module that is incompatible.

also: the aurelia-commands seem to require gulp version 4.0.0, but version ^3.9.1 is listed in the devDependencies.

@Alexander-Taran
Copy link
Contributor

@JeroenVinke how can this issue be improved to be actionable?

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