Open-source project
yeoman/generator-webapp avatar
yeoman/generator-webapp

generator-webapp: version 4.0.0 was never tagged, and the engine floor says Node 6

GitHub describes it as A gulp.js generator for modern webapps. The repository metadata lists JavaScript as its primary language. This article stays within the project description and details documented in the GitHub repository README.

3,734 stars693 forksJavaScriptLicense varies

At a glance

What is it?
generator-webapp is a Yeoman generator that scaffolds a front-end project with gulp as the build tool, and it is effectively frozen: the newest release is the ninth prerelease of a 4.0.0 that never shipped, the last commit is from January 2024, and the manifest still declares Node 6 as its engine floor while the toolchain behind it needs a decade newer. The README tells you to read the generated gulpfile for what is actually supported.
Who is it for?
This generator is worth reading if you want to see what a gulp-based front-end scaffold looked like, or if you already depend on it and need to know what you are pinned to. It is not worth starting a project on.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Probably not. The repository last received commits 34 months ago, on January 30, 2024.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • yeoman/generator-webapp3,734 ★ · -10
Star history
Repository2026-08-132026-11-15
yeoman/generator-webapp3.7k3.7k

-10 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The stable 4.0.0 was never tagged

The release list explains the version in the manifest. There is v4.0.0-7 from November 2019, v4.0.0-8 from March 2020, and v4.0.0-9 from January 2024, which is both the newest tag and the version string in the package manifest. No 4.0.0 without a suffix was ever published, so the counter has been incrementing on a prerelease for six years, with a four-year gap between the eighth and ninth. The file addresses this directly with a banner at the top: there is a pre-release version of the generator, it can be installed with a pre-release npm tag, and readers are asked to report bugs to help make it stable. That instruction has been sitting in the same place across the whole gap. The last commit to the default branch is dated 30 January 2024.

The engine floor says Node 6 and the toolchain says otherwise

The manifest declares an engine requirement of Node 6 or later, which dates the project to 2016 by its own account. The development dependencies say otherwise: a linter in its 5.x line, Prettier in its 1.x line, a test runner in its 6.x line, and a Git hooks package in its 2.x line, none of which will install or run on anything close to Node 6. So the declared floor describes a compatibility promise the project cannot keep, and a reader who trusts it will get a resolution failure rather than a working generator. There is a second mismatch of the same kind in the hooks: the pre-push and pre-publish hooks invoke yarn to run the lint and test scripts, while every user-facing instruction in the file is npm, and a yarn lockfile is committed at the root.

Both test framework generators are hard dependencies

The runtime dependency list installs two competing test framework generators, one for mocha and one for jasmine, unconditionally. The choice the user makes is the `--test-framework` option, which accepts either name and defaults to mocha. So a user who picks mocha still installs the jasmine generator and its transitive tree, because the decision is made at generation time while the dependency is paid for at install time. The same list also pins a directory creation library at a 0.5 release, several major versions behind its current line, and the Yeoman generator framework itself in its 4.x line. This is the pattern where a scaffold's dependency list ages as a set rather than being maintained piece by piece.

The supported feature list lives inside the templates directory

The feature list in the file is a summary with a disclaimer attached to it, and the disclaimer is the important part: for up to date information on what is supported, you are pointed at the gulpfile in the templates directory, and for the plugins, at a package manifest fragment in the same place. The bullets themselves cover enabling modern JavaScript syntax through Babel, CSS vendor prefixing, a preview server, Sass compilation, script linting, source maps from compiled CSS back to source stylesheets, and image optimization. Each of those is really a gulp plugin listed in a template that will be copied into the generated project, so the README is describing a file the reader has not downloaded yet. Two of the bullets are also written as the project's own marketing rather than as a specification.

Switching Sass implementations means editing the generated gulpfile

The one substantive caveat in the file is about the Sass compiler. The bundled implementation is not feature-wise compatible with the Ruby original, and the reader is pointed at a curated list of incompatibilities to find out what is missing. The escape hatch is a different gulp plugin, and applying it is a manual edit: you update the styles task in the generated gulpfile. So this is not an option exposed at generation time, it is a code change inside a project you have already scaffolded, which means the generator cannot be re-run without losing it. It is also the clearest signal of the project's age in the whole file, since the choice is between two implementations of a tool that later moved again.

Two documented commands carry a double space

The getting started list is a set of commands with a consistent port convention: the preview server on one port, the browser tests on another, and the production preview on a third, each with a variant that takes a port flag. Two of those lines contain a double space between the run keyword and the script name, and both are the browser test lines. npm tolerates the extra space, so the commands work, but it is the kind of detail that gets copied into a wiki and then into a script. The install line is also worth reading carefully: it installs the Yeoman CLI, the gulp command line wrapper and this generator globally, which means the scaffold depends on a global toolchain rather than only on project-local dependencies.

The keywords still list jQuery and Modernizr

The manifest keywords are a fossil record. Alongside the generator and web terms, they name an HTML5 boilerplate template, the Modernizr feature detection library, jQuery, and gulp. So a scaffold whose headline feature is transpiling modern JavaScript syntax through Babel still identifies itself with two libraries from the previous decade, which is consistent with a template lineage that predates the ES2015 work. The tree matches the story: an app directory holding both the generator and its templates, a test directory, a docs directory, a screenshot image, an editor config, an ESLint config in YAML form with its own ignore file, and a repository directory for contributions. There is no licence file in that listing, although the manifest declares BSD-2-Clause and the file links the BSD licence text.

Editorial conclusion

This generator is worth reading if you want to see what a gulp-based front-end scaffold looked like, or if you already depend on it and need to know what you are pinned to. It is not worth starting a project on. Four things to weigh. The stable release never arrived, so installing the default tag and installing the pre-release tag give you different generators, and the README's own instruction is to install the pre-release one. The engine floor declares Node 6 while the development toolchain needs something far newer, so the declaration tells you nothing useful. The supported feature list lives in a file inside the templates directory, which means the summary in the README can drift from what a scaffold actually contains. And the build tool itself, gulp, has been superseded by tooling this project does not mention.

Frequently asked questions

What is this Yeoman generator used for?

It scaffolds a front-end web app whose build is driven by gulp, then hands you a project with preview, lint, browser test and production build commands. Generated projects get Babel for modern JavaScript syntax, CSS prefixing, a preview server, Sass compilation, source maps and image optimization, with the exact plugin list defined in the template's gulpfile.

Which test framework does generator-webapp use?

Either, chosen with a test-framework option that accepts mocha or jasmine and defaults to mocha. Both generator-mocha and generator-jasmine are listed as dependencies of the generator itself, so both are installed whichever one you pick.

What is the latest version of generator-webapp?

The newest tag is v4.0.0-9 from 30 January 2024, the same day as the last commit, and that prerelease is the version in the package manifest. A stable 4.0.0 was never tagged, and the file asks readers to install the pre-release npm tag and report bugs.

Official sources

  1. Official README
  2. Project repository
  3. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/yeoman-generator-webapp.svg)](https://hysenlabs.com/projects/yeoman-generator-webapp)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/yeoman-generator-webapp.svg)](https://hysenlabs.com/projects/yeoman-generator-webapp)

Was this useful?