theleebriggs/deja-dev

Generator for web projects.

Déjà Dev ⌛

We've been here before, let's save some time shall we? An opinionated generator for web projects.

What ☝

An attempt to document the evolution of stacks I use on projects. Rather than my normal copy+paste+delete as required. This generator will scaffold out starting points for various stacks.

Built using the SAO framework.

Stacks ⚡

• Front end
  • NextJS
  • Theme UI
• API (coming soon)
• Fullstack (coming soon)

Usage 🚀

npx sao theleebriggs/deja-dev -u my-project

TODO 💅

Templates

• Common

  • LICENSE
  • .gitignore
  • .gitattributes
  • .editorconfig
  • .nvmrc

• FE App

  • NextJS
  • Typescript
  • Styled-Components
  • ThemeUI
  • Linting (Stylelint?)
  • Prettier
  • .env files
  • react-testing-lib
  • Cypress
  • Storybook

License

MIT © theleebriggs

deja-dev's Issues

Engine management setup to prevent version bugs

Sometimes I lose time debugging errors caused by using the wrong package manager, for e.g. npm instead of yarn, or the wrong version of node or the package manager. For e.g. trying to run a new kind of command in an older version of yarn and it not working.

Could including something like this in the project setup help prevent these kind of problems?
https://docs.npmjs.com/files/package.json#engines

Or this:
A one-liner in the scripts of the root directory will make npm install explode if you try to use it.

"preinstall": "node -e \"if (process.env.npm_execpath.indexOf('yarn') === -1) throw new Error('Use yarn for installing: https://yarnpkg.com/en/docs/install')\""

Or this:
This looks like it checks that you used yarn in a postinstall hook, but maybe not a great solution? https://github.com/alexanderwallin/use-yarn-instead