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

Generating new app prints a warning about Jade #166

Open
tjwebb opened this issue May 4, 2016 · 6 comments · May be fixed by #246
Open

Generating new app prints a warning about Jade #166

tjwebb opened this issue May 4, 2016 · 6 comments · May be fixed by #246
Assignees
Labels

Comments

@tjwebb
Copy link
Member

tjwebb commented May 4, 2016

Issue Description

Occurs after I run yo trails:

npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade

Environment

  • node version: all
  • trails version: all
  • operating system: all
@tjwebb tjwebb added the ux label May 4, 2016
@jaumard
Copy link
Contributor

jaumard commented May 10, 2016

@weyj4
Copy link
Member

weyj4 commented May 10, 2016

What trailpack requires jade? I think that's coming from mocha?
mochajs/mocha#2200

@jaumard
Copy link
Contributor

jaumard commented May 21, 2016

We can't do anything about this as mocha is used by all trails modules ^^ and they doesn't seems close to upgrade to pug after reading the @weyj4 issue.

@jaumard
Copy link
Contributor

jaumard commented Jul 27, 2016

@tjwebb @weyj4 mocha v3 will move to pug :) and it will be publish in few days if all is ok mochajs/mocha#2350

@jaumard
Copy link
Contributor

jaumard commented Aug 17, 2016

mocha v3 is out we can migrate to this version and remove jade warning :)

@scott-wyatt
Copy link
Member

@jaumard fantastic job keeping on top of this!

@catrielmuller catrielmuller linked a pull request Oct 14, 2016 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants