-
-
Notifications
You must be signed in to change notification settings - Fork 543
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
Default view engine to pug, not jade. #166
Comments
Hi @fluxsauce I would say this is a duplicate issue for the one you linked to. Certainly replacing jade with pug is up for consideration, but pug still hasn't actually released a stable version yet, and has been constantly in flux, from being in alpha forever, then beta forever and now sitting in RC. |
Additional information from that issue in why we have not changed it yet is because there are many tutorials out there that say |
If you can help get tutorials updated, that would be a big help as well 👍 |
@dougwilson can you be more specific, IE which tutorials are you speaking of? |
There are a lot out there, and I've gotten a lot of them changed and am basically just trying to get the ones that are at the top of the Google search results. For example:
Getting the tutorials that at least turn up at the top of search results has come up multiple times by folks not even involved in Express #141 (comment) and #141 (comment) |
how about now? https://www.npmjs.com/package/pug/v/2.0.4 |
https://pugjs.org/api/migration-v2.html
The package should be updated and the templates should be renamed as well.
Sorry for the potential duplicate; after I submitted this, I noticed #141
Honestly, the deprecation warning is pretty gnarly and since Pug is Jade, I think it's logical to just rip off the bandaid and do it rather than rabbit-holing on alternatives.
The text was updated successfully, but these errors were encountered: