The dependency prop-types was updated from 15.6.2 to 15.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prop-types is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Currently we have https://pugjs.org/api/getting-started.html, which assumes you are using the pug api. This is almost certainly not what most people are doing. We should ideally offer an experience similar to https://babeljs.io/docs/setup/ showing how to use it with node, CLI, gulp, grunt, etc.

Version 1.6.10 of js-beautify just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As js-beautify is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

pugjs/pug#2754

At first glance, it seems like the repositories pug-www, pug-en, and pug-zh-cn might all be the same thing. I mean, I think I was able to figure it out: From looking through the pug-www and pug-en repositories, I gather that the Pug documentation repos contains most of the actual content (the language and API spec), and the Pug website repo adds some extra templates and scripts for presenting the documentation online. Still, it might help to state in their respective READMEs what role each repository serves. Users who see a typo in the documentation, or a bug in the interactive code examples, might rush to the wrong repository and get confused.

We should provide a simple language picker somewhere in the layout, so people can change languages.

We need a landing page for https://pugjs.org, instead of dropping users directly to the API intro. Specifically, I envision the page to have

• Jumbotron-level logo & tagline
• a simple demo
• introduction to a few core features of Pug, like tags, attributes, mixins

Update the code in https://github.com/pugjs/pug-www/blob/master/templates/index.pug#L4 so that we automatically detect the user's language. If available in https://github.com/pugjs/pug-www/blob/master/langs.js we should then redirect the user to their preferred language. Ideally we would do this for all users by default (unless they explicitly select a given language, see #17)

We need to load content from https://github.com/pugjs/pug-{language}/ when it's not available locally. This is what will happen in the travis deployment. I suggest a few refactorings:

• have the markdown module actually just render markdown
  • pull file reading/lookup out of the markdown module
  • pull rendering pug template out of the markdown module
  • pull loading strings out of the markdown module
• Don't generate browserify bundles on the fly (https://github.com/pugjs/pug-www/blob/master/src/index.js#L23-L32) as this is really slow even for development. I'm not even sure if we need this. By writing it this way, the bundle gets built once for each request. In addition to this, each time you build it you are setting up a file watcher to rebuild every time the bundle changes.
• serve the default language (i.e. en) with no /en/ url prefix
• do not force browserify into development mode. This is probably what keeps the server alive after calling server.close(). We can manually disable minification as appropriate, but should do that separately.
• use somewhat fewer promises. File system operations do not need to be async because this will be static once it's hosted. On the other hand, many of our file system operations will turn into reads from GitHub repos, so they will be async anyway.
• create a clean separation between server and client code
• support running in more environments by moving away from sass which requires a native module

Version 1.5.0 of resolve was just published.

This version is covered by your current version range and after updating it in your project the build failed.

resolve is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency express was updated from 4.16.4 to 4.17.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

express is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

In this code I continue a table with the results of a database search

extends wineSearch

block content
   for val in wineSelection
      tr
         td
            form(action='/wine/update', method='POST')
               input(type='hidden', name='loc', value=val.wine_Location)
               button.loc_button=val.wine_Location   
         td= val.wine_Quantity
         td= val.wine_Type
         td= val.wine_Colour
         td= val.wine_Grape
         td= val.wine_Winery
         td= val.wine_Country
         td= val.wine_Vintage

In chrome the first row, the form is excluded. Remaining rows are correct. Testing using Postman yields the correct result

Chrome: (error)

						<td>
							<input type="hidden" name="loc" value="E1" /><button
								class="loc_button"
							>
								E1
							</button>
						</td>

Postman: (correct)

<td>
						<form action="/wine/update" method="POST">
							<input type="hidden" name="loc" value="E1" /><button
								class="loc_button"
							>
								E1
							</button>
						</form>
					</td>

I am sure that the input to PUG is the same. ie wineSelection
Does the express server detect the client and render differently?
Is there a way to force the render as if a Postman client?

Currently this project doesn't have a license. This could especially be useful for others wanting to use the pug logo.
I would recommend a CC3.0 variant

We need a good solution for identifying sections of the page that our out of date. We could assume that any given page is out of date if the english version of the markdown file has been updated more recently than the translated version. Ideally this would offer a link to the english version, and a link to edit the translated version so people can update them.

Version 7.3.0 of eslint-plugin-react just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-react is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hi, I had to translate most of pugjs documentations contents in French for our PHP port documentation https://phug-lang.com

So now, I could easily translate your whole documentation if you set-up for me the pug-fr repository.

You can rely on my level in French, it's my mother tongue and I master it well.

This page should look along the lines of:

react-pug

You can use pug to generate react templates. This is supported via a babel-plugin. To use it, you need the following two plugins in your .babelrc:

{
  "plugins": [
    "transform-react-pug",
    "transform-react-jsx"
  ]
}

You can install them via:

npm install babel-plugin-transform-react-pug babel-plugin-transform-react-jsx --save-dev

Usage

To use react-pug, you just declare a tagged template literal:

import React from 'react';
import ReactDOM from 'react-dom';

function HomePage() {
  return pug`
    div
      h1 Home Page
      p Some content
  `;
}

ReactDOM.render(
  pug`HomePage`,
  document.getElementById('container'),
);

babel-plugin-transform-react-pug will convert the pug code in template literals into JSX.

Editor Support

In brackets you just install the pug plugin. In atom, install language-babel and the pug plugin, then configure the template literal tag in langauge-pug (this needs documenting properly).

Chrome Version 52.0.2743.116 (64-bit)
OSX 10.11.6

We should consider redirecting HTTP (http://pugjs.org/language/filters.html) to HTTPS (https://pugjs.org/language/filters.html).

Version 15.6.2 of react-dom just got published.

This version is covered by your current version range and after updating it in your project the build failed.

react-dom is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Why have you forked stop? Can you contribute your changes to https://github.com/ForbesLindesay/stop

Hey, I've noticed that the Nested Filters section–which brings an example where the script is first transformed by babel, and then by cdata-js–outputs:

_.default.existsSync is not a function

As can be seen here:

I admit I haven't read the source yet to find the problem–that's why this isn't a PR.

I wonder if maybe what I'm reporting here isn't a mistake of mine-then please point and I'll close the issue ASAP 😄 .

Maybe you should check the integrity of Bootstrap's components...

Version 5.24.2 of codemirror just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As codemirror is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

It seems like either we want this everywhere, or not at all.

Version 15.6.2 of react just got published.

This version is covered by your current version range and after updating it in your project the build failed.

react is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

This was posted long time ago at this link, reposting.
pugjs/pug#3132

Hey, I spent 1 hour to find out why my Webstorm File Watcher could not detect pug. I had installed Node.js, Express.js.
What I was missing was commandline installation instruction, which was not visible in the website.

Only in the github website I found it, and at the the I didn't even know what the question and solution was supposed to be.

So could you please also write the Command Line installation instructions from Github shown below in your website, that would save a lot of time. Thanks.
https://pugjs.org/api/getting-started.html

Command Line
After installing the latest version of Node.js, install with:

$ npm install pug-cli -g
and run with

$ pug --help