Open davidsharp opened 8 years ago
I'd take a PR to upgrade to Pug but still handle Jade file extensions
Also note that Pug 2 was released in August 2016 (the tags on the github repo claim it's beta, but according to their docs it's a full release).
When installing electron-prebuilt-compile
you get a warning saying jade
is deprecated:
npm WARN deprecated jade@1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
So I guess, it should be replaced.
Is anyone working on a PR for this? If not I wouldn't mind taking a stab at it. It looks straight-forward, and I love to eliminate warnings like these because they drive me nuts.
Looks like there was something a while ago here but then things got quiet.
When will this be complete?
This will be helpful: https://pugjs.org/api/migration-v2.html
@Hum4n01d, seems like it depends on the release of Pug 2.0. It's still in beta.
Ok. I'm just writing pug and using the .jade extension. They're mostly the same.
On Jul 2, 2017, at 11:43 AM, Josh Beckwith notifications@github.com wrote:
@Hum4n01d, seems like it depends on the release of Pug 2.0. It's still in beta.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Released now, so hopefully we can get this done.
Assuming this never happened? Any work arounds?
It doesn't look like electron-compile is still being developed, based on the fact that no commits have been made since September 2017
Ya I just decided to compile my own. Seems electron-forge still relies on this though. Wonder if I should keep using it.
News?! 😢
Jade's undergoing a name change, and is becoming Pug.
Therefore, It'd be nice if there was support for
.pug
files. Naturally, Jade support should probably stay for now, but this will only become more of an issue as Pug becomes established as the new home of Jade.https://github.com/pugjs/pug