Unfortunately, as per #2184 we need a new logo. The original discussion around the logo was in #1882.

@GarthDB and @viktorbezdek have both volunteered to help with the designs.

We can dramatically improve performance if we don't use with.

We achieve a similar effect to with using the global object from a separate module.

This improves performance by a factor of 3.

Hi, i'm a fan of jade

I'm in progress with my sublime-text theme project: sliver.

I'm a about to write down the sidebar icons, and I've noticed that there is no official jade icon...

I know is not a big issue, but I was wondering if it was planned...

Thanks in advance!

closes #875

If we can remove this feature (probably in 0.32.0) then it will simplify a lot of code and significantly reduce the amount you have to learn when you're new to node.

The first step to removing it is to deprecate it and discourage people from using it, so this pull request logs a warning whenever someone relies on this feature. Dealing with the fallout from this will also help to gauge how many people we're going to annoy by removing this feature.

Crucially, once we actually remove the feature altogether, we will be able to write templates that do things like:

script
  import foo.js

which would be enormously useful.

I would like to be able to write my markup like thus:

//panel.jade

section.panel
  block head
    header
      h1.title!= title
  .content
    yield

invocation:

//some_file.jade
    include panels/panel
      block head
        //nothing
      img( src="#{work.urls.main}/poster_280.jpg" )

Update based on feedback the new proposal would be:

//panel.jade
mixin panel
  section.panel
    block head
      header
        h1.title Default
    .content
      yield

invocation:

//some_file.jade
    + panels/panel
      disable head
      img( src="#{work.urls.main}/poster_280.jpg" )

So instead of having to do:

   div
      | some text
      code some code
      | and some text

maybe we could do:

   div some text [ code some code ] and some text

so it would treat everything inside the [ ] as it's own line then continue with the text node

not sure if this is a silly idea, thought id throw it out there

I think there are a number of things that could be done to improve filters enormously. I'm mostly using Jade for static site generation, so filters are one of the most important features for me as they allow me to do things like write the actual posts in markdown.

Use transformers

transformers is like consolidate.js except that it supports synchronous rendering where possible (it almost always is) and it has a few things that are not really tempting languages (markdown, coffee-script, cdata and uglify-js).

Over time, separating filters out into a separate library like this would allow the collection of possible filters to explode as a result of being able to share their implementation with many other libraries.

Each transformer also has an .outputFormat (xml, css or js) which can be used to work out what kind of script/style tags to wrap the result in.

Filtered includes

I would like to support filtering an included file:

:markdown include path/to/markdown.md

Filtering Filters

This needs to be clever enough not to keep wrapping the result in an additional <script> or <style> tag each time (it should only do that for the last filter):

:uglify:coffee
  my coffee script

Runtime filters

I would like to have filters sometimes be compile time and sometimes be run-time. They'd be compile time where possible, and only fall back to run-time when necessary.

This would allow the following significant use cases:

The following escapes foo then transforms it using filter before buffering it (all at runtime):

:filter= foo

The following transforms foo using filter before buffering it (all at runtime):

:filter!= foo

The following passes {user: user} to the filter EJS and runs it at run time.

:ejs(user=user)
  <%- user.id %>

The following passes {compress: true} to the filter less and runs it at compile time

:less(compress=true)
  .less-styles {
    background:blue;
  }

At compile time

:uglify(mangle=false):coffee(bare=true)
  some coffee script

Similar to how this works in Jade:

input(
  type='checkbox'
  name='agreement'
  checked)

I'd like to be able to do this:

config = {
  a: 'something',
  b: 'something-else'
}

instead of having to write:

config = { a: 'something', b: 'something-else' }

This is a short example, however as config grows it would be much prettier if funky spacing was allowed.

I'm wondering if there is any way to populate the attributes on an element from the keys/values on an object. What I really want to do is something like this:

input.foo(name=name, value=value, attributes)

Pass in data like this:

{
    name: 'username',
    value: 'bob',
    attributes: {
        maxlength: 16
    }
}

and get this output:

<input name="username" value="bob" maxlength="16" />

Is there any way to accomplish this without needing to specify each attribute individually?

Unfortunately, these people have a trademark for the word "jade" referring to software, so we've been forced to change our name. Fortunately, @davidglivar has kindly donated the name "pug" to us. I've claimed pug and pugjs everywhere I could think of so hopefully we shouldn't have any problems getting the name.

Action items

• [x] create a new logo (@GarthDB)
• [x] design new branding for the website (@GarthDB)
• [x] develop new website
• [x] rename all repositories
• [x] update every reference to "jade" to refer to "pug" in all repositories
• [x] add @TimothyGu as an owner of all "pug" related npm repos
• [x] publish working alpha-release
• [ ] test and stabalise release
• [ ] release pug 2.0.0

Versioning & Deprecation

There will be no 2.0.0 release of jade, instead it will be released as pug 2.0.0. In the mean time, pug 0.10.x will be used for experimental releases of pug 2.0.0 until it is stabilised.

Existing versions of jade will be left working for at least 6 months. There may be a [email protected] release aimed at being as compatible as possible with [email protected].

The new website will be at www.pugjs.org (which I have registered). Once that website is built, http://jade-lang.com/ will be updated to redirect to www.pugjs.org

FAQ

Why pug?

It's short, memorable and widely available. Not only that, but pugs are cute!

Do we really have to change the name?

Yes. The stress of pursuing this through the courts would be too high. I would much rather focus my efforts on writing great software, and supporting the people who use pug.

Couldn't we just change the name to ?

Maybe, but I like pug, and it's definitely available. If your suggestion was along the theme of "make a one letter change to jade", I think it's preferable in the long run to make a clean break and start with a nice fresh brand.

more questions (and answers) will be added as they are asked

Much like the new multi-line attributes, I think it would be very nice to have the ability for multi-line code blocks. I hate going beyond 80 chars per line and sometimes with partial rendering or a condition, things get a little long.

!= someAwesomeHelper('param1', 'param2'
                     'params3', 'param4')

Pug Version: Latest Node Version: LTS 16.13.1 at the time

Description

I'm trying to use pug walker to create our own internal linting utilities, but the walker doesn't provide a way to get access to the node parent element like babel or eslint.

Pug Version: your version number here @latest Node Version: your version number here 12.22.12

Input JavaScript Values

N/A

Input Pug

N/A

Expected HTML

N/A

Actual HTML

N/A

Additional Comments

Pug installation is failing on npm or yarn with node v12 due to

error An unexpected error occurred: "https://registry.yarnpkg.com/acorn/-/acorn-7.4.1.tgz: incorrect data check".

Pug Version: 3.0.2

Node Version: 18.12.0

I have project using Express with pug then I found a strange behavior on my view. They somehow access some variable I didn't declare/pass. After a bit digging I found out that pug somehow be able to access controller variable that haven't declare with a var/let/const keyword. I'm not sure is it a bug or a feature.

Input JavaScript Values

module.exports = {
    renderLogin: (req, res) => {
        test_variable = "This variable has been passed"
        res.status(200).render('login', {
            message: req.query.message,
            icon: req.query.icon,
            alert_type: req.query.alert_type,
        });
    }
}

Input Pug

.container-fluid.vw-100.vh-100.bg-light
   h1=test_variable
   // - other form stuffs
  

Render view

Better support for i18n is needed inside pug templates. For now I found the solution but it's a bit complex and confusing. I though pug processor is one of the natively supported engines for i18n.

Pug Version: "^3.0.2", Node Version: v14.15.4

Input JavaScript Values

// server level app.use(function(req, res, next) { // express helper for natively supported engines i18n.init(req, res); res.locals.__ = res.__ = function() { return i18n.__.apply(req, arguments); }; next(); });

// Module level const pug = require('pug'); const func = pug.compileFile('pug/test.pug'); function foo(req, res) { let msg = res.__('Hello'); let ins = func({ message: msg, : res. }); // << I have to add this to every render request res.end(ins); }

Input Pug

p #{msg} p #{__('Hello')}

Expected HTML

Localised output (based on browser locale)

Actual HTML

Localised output (based on browser locale)

I finally made it work, but there should be an easier way to do it.

I'd like to say thanks for all the time and effort you've put in over the years. I've used jade/pug across many projects and companies and have a lot of love for it. With that being said, it doesn't seem like pug is maintained at this point. It's completely understandable if you're busy or have simply moved on to greener pastures. Whatever the reason may be, is it possible to get an official status update on pug @ForbesLindesay?

On a side note, would donations to pug's Open Collective page make any difference, or is pug considered pretty much done/inactive at this point? I'm assuming there is no v4 in the works but was hoping to get some kind of confirmation in terms of pug's future or perhaps a notice added to the readme / npm package.

Thanks (and much ❤️ for 🐶)!