Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

• Maybe split this into a couple subgenerators
• Create a REST structure
• HTTPS support
• Work with static-site stuff
• Option for REST only server

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Add Redux to subgenerators

• Static-site (both with and without React)
• Maybe even in the generic projects since Redux is fairly easy to debug and test

Amazing documentation for the package: https://redux.js.org/

• Support es6+ syntax
• Use webpack transpiler
  • Separate configurations for production and development
• gulp, gulp-sourcemaps, browser-sync
• ejs, htmlmin
• less, autoprefixer, cssnano, postcss
• testcafe UI testing

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

JSDoc-to-Markdown has a security vulnerability in it's handlebar version used. Although it's not exactly used in the build, I don't want to constantly tell GitHub to not worry about it in new projects.

https://github.com/documentationjs

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Add react-mini.css component library to the dependencies for static site projects using React. Since the generator uses Mini.css as the default css framework.

Also add a little snippet of code to the starter index.js file using one of the components.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Add TypeScript to do type checking for JavaScript files. I'd like to add more static checking. It would also allow editors, such as VS Code, to automatically perform the checks.

Technically this is being done with the generic subgenerator, but this should be actually redefined as the default subgenerator.

• Add start script
  • "babel-node index.js" since babel-cli is a dependency
• Create .npmignore file
  • src directory is included
• Option to include a cli portion
  • Include starter cli.js file
  • Add commander and chalk packages to dependencies
• Add command name to bin section of package.json
  • Defaults to project name

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Jest requires a different version of babel-core to work with the latest babel version (v7).

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Update configurations to use Babel v7.
No more stage presets as well.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

• This should add the babel-polyfill code snippets so that web apps can generally work on any non-dead browser.

• Also, use "defaults" for the browser target. It's much better than the current configuration.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Instead of placing all of the files into the current directory, offer the option to place them all into a new directory.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

I want to keep this generator updated for as long as possible. This score may seem a bit superficial, but it does point to possible maintainability issues.
This may just involve creating utility functions to shorten some files.

• Use nodejs versions "node", 7, 6 for environment
• Run `npm test'
  • Run 'npm run buildandnpm run test:ui` for static-site subgenerator
• Option to send code coverage report to Coveralls
• In static-site generator, option to deploy to GitHub pages from master branch on test success

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

GraphQL has been pretty great to work with while using GatsbyJS. It might be nice to offer this API type in addition to REST.

Article: https://medium.com/@gethylgeorge/setting-up-a-simple-graphql-server-with-node-express-and-mongoose-ff8a1071af53

These files could probably be based off of the ones found in this project

• CODE_OF_CONDUCT.md
  • The template should receive the user's email
• Add CONTRIBUTING.md
• Add docs/ISSUE_TEMPLATE.md
• Add docs/PULL_REQUEST_TEMPLATE.md

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Due to the security issues and a weird bug that doesn't end the UI tests, I'm deciding to remove TestCafe for now. It also seems to be a bit of an overkill to include full UI testing on a brand new project.

Referencing:

• https://david-dm.org/DevExpress/testcafe

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

With Babel v7 being able to transpile TypeScript, it should be easier to integrate with the rest of the build configurations.

This will only be meant for the front-end portion. This is because I don't want to add a build step on the server code -- for now. I might feel different about this later.

After using TypeScript for as long as I did, I'm pretty satisfied that it helped so much. It encouraged me to document my functions more often than I did in the past.

Luckily, most tools also support TS, albeit with a little more configuration. But I only really need to do that once for here.

Standard: https://standardjs.com/#can-i-use-a-javascript-language-variant-like-flow-or-typescript

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

The service worker should support a cache-first strategy and offline access. The cache should be updated in the background.
Add other PWA related files.
Possibly related to #14

Resources:

• https://developers.google.com/web/fundamentals/primers/service-workers/
• http://www.pwabuilder.com/generator
• https://github.com/pwa-builder/serviceworkers/blob/master/serviceWorker4/pwabuilder-sw.js

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

JSHint offers a bit more power than just the Standard linter.

Currently, the tests just check for the presence of generated files.

• Test for content of generated files affected by user input.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Better Code Hub keeps marking concerns about the long gulpfiles.
Gulp-hub should be a pretty good solution to break them down.
Other gulp solutions don't work for the updated version.

https://github.com/frankwallis/gulp-hub/tree/4.0

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Node version 8+ already has all the language features I use. It only adds import/export capabilities; even then, it converts it to just module.exports = {...}. I can give that part up.

Also, by removing the babel step, I can start using Node's debugger with VS Code.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Add Netlify-specific features in the static-site subgenerator.

• Functions (AWS Wrapper)
• Identity

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Okay, so this has a specific use case. This would make a static site that uses packages to make a slideshow. This might be easier to build with React as well.

• frappe-charts
• reveal.js

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

This is a separate issue given that each subgenerator has a distinct set of tasks.
Refers to the solution for #19

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

• The only reason babel-register should be added is for testing.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Reorganize feature section to be easier to read.
Add server project type to list

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

This would have both the server and client components in one project.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

gulp-webpack was renamed webpack-stream a while ago. The usage is still the same, but getting the updated version of the package is probably important.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Add the achieved features in the README file. Just make it more detailed for anyone else who uses the tool.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Add img directory for images to be processed.
Add a directory for all favicons

References:

• https://realfavicongenerator.net/
• https://github.com/sindresorhus/gulp-imagemin

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

While it's nice to have husky and lint-staged set up for any later projects, they aren't necessary for one-off coding sessions. Not every project will be published.

Provide this as an option. Default to no.

• Update package.json on subsequent calls to the generator (or if calling on existing project)

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

• Missing extract-text-webpack-plugin@next
• Use html-webpack-plugin@latest
• Use webpack-dev-server@latest
• Change dev script to webpack-dev-server --config webpack.dev.js --open
• Change .babelrc to use babel-preset-env and babel-preset-react instead of the scoped @babel versions

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

JSDoc generates API documentation based on block comments. It's an efficient way to record changes.
The provided link points to a package that outputs the documents in markdown files.
Usage with gulp is preferred.

https://github.com/jsdoc2md/jsdoc-to-markdown
https://github.com/jsdoc2md/jsdoc-to-markdown/wiki/How-to-use-with-gulp

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Switch to mini-css-extract-plugin from extract-text-webpack-plugin.
mini-css-extract-plugin already supports webpack 4, while the other is still in beta.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Sometimes speed is key. Add some template files and additional dependencies to enable Rust bindings.

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

To sure the coding styles in files are consistent, it might be good to run the linters on each commit.

Packages to use: husky, lint-staged

Reference: https://medium.com/@bartwijnants/using-prettier-and-husky-to-make-your-commits-save-2960f55cd351

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

The commit hooks information is placed inside another object in the generated package.json

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

The module does not take in relative paths that go up one directory apparently. Must make the following change:

server: path.resolve(__dirname, '../dist')

Before you submit an issue:

• Check for similar issues
• Provide error messages, if applicable
• Feature requests/suggestions are always welcome for discussion
• Title the issue appropriately

Description

Add caching into gulp and webpack to speed up task/build times.

• Add CONTRIBUTING.md
• Add ISSUE_TEMPLATE.md
• Add PULL_REQUEST_TEMPLATE.md