• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Currently the following message is printed after init:

VS Code users: run 'Extensions: Show Recommended Extensions'

This should instead (or as well as) be added to the DEVELOPING.md file(s)

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

https://github.com/sindresorhus/conf

✨ Enhancement Request

It's easy for ADR titles and file names to become out of sync. Fix this with a script that writes the ADR title to the filename, and run it automatically on changes.

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters
• Ready for review

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Move husky settings into package.json

The setting is so minor, is just an alias to npm run pre-commit, and will never be changed.

"husky": {
    "hooks": {
      "pre-commit": "npm run pre-commit"
    }
  }

✨ Enhancement Request

It's possible for files to go unformatted.

The npm run lint command should alert to this issue.

Can use --list-different option with Prettier. However, we have other formatting tools besides Prettier. Perhaps the best way is to run npm run format and check if any files changed. However, this means the git must be clear. Perhaps this should only be run during CI.

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters
• Ready for review

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Upgrade to Jest 24.

It includes built-in TypeScript support.

Hopefully can simplify the configuration, and possibly remove babel-jest dependency

Enhancement

When hovering over an issue in GitHub, the first few lines are displayed. Currently this displays the checklist. It would be better to display the actual issue.

Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Requires tweaks to Babel config (ignore if NODE_ENV is not test), and typescript configs

✨ Enhancement Request

Keep your manual linting overrides to yourself

Use eslint-config-iamturns as a central repository to store these rules instead. Potentially use it within the src directory, but definitely not within template directory.

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters
• Ready for review

What

Prettier plugin sort imports
A prettier plugin to sort import declarations by provided Regular Expression order.

https://github.com/trivago/prettier-plugin-sort-imports#readme

Why

TBD

How

TBD

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.

Enhancement

Ask for name and email address.

Default to settings in git config.

🐛 Bug report

Tests within dist directory are run. They should be ignored.

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate bug reports.
• Title is a summary of the bug report, in present tense, and ideally < 50 characters
• Ready for review

🐛 Bug report

On commit 8755684
I run create-exposed-app-cli.js
I try add all those files to git and commit - git commit -m "Add files"
error mesage:
` ✖ markdownlint
Running tasks for /.{css,gql,graphql,html,json,less,md,mdx,scss,vue,yaml,yml}
Running tasks for **/.{js,jsx,ts,tsx}
Running tasks for src//*

✖ markdownlint found some errors. Please fix them and try committing again.

/home/dewi/tempdewi/test6/docs/adr/README.md: 5: MD041/first-line-h1 First line in file should be a top level heading [Context: "- ADRs"]`

Supporting both TS and JS is adding unnecessary weight to the project.

Instead, assume TS by default. It can be easily removed and converted to JS if needed. Possibly provide instructions for this.

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Apply imagemin to image files automatically.

See: https://github.com/tomchentw/imagemin-lint-staged

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): replace dependency npm-run-all with npm-run-all2 5.0.0
• chore(deps): update dependency @types/debug to v4.1.12
• chore(deps): update dependency doctoc to v2.2.1
• chore(deps): update dependency eslint-config-airbnb-typescript to v16.2.0
• chore(deps): update dependency eslint-config-prettier to v8.10.0
• chore(deps): update dependency eslint-plugin-jsx-a11y to v6.8.0
• chore(deps): update dependency eslint-plugin-promise to v6.1.1
• chore(deps): update dependency eslint-plugin-react to v7.34.1
• chore(deps): update dependency markdownlint-cli to v0.40.0
• chore(deps): update dependency prettier to v2.8.8
• chore(deps): update dependency sort-package-json to v1.57.0
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency eslint-config-airbnb-typescript to v18
• chore(deps): update dependency eslint-config-prettier to v9
• chore(deps): update dependency eslint-formatter-pretty to v6
• chore(deps): update dependency eslint-plugin-jest to v28
• chore(deps): update dependency eslint-plugin-unicorn to v52
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency sort-package-json to v2
• chore(deps): update dependency typescript to v5
• chore(deps): update googlecloudplatform/release-please-action action to v4
• chore(deps): update jest monorepo to v29 (major) (@types/jest, babel-jest, jest)
• chore(deps): update stefanzweifel/git-auto-commit-action action to v5
• chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• chore(deps): update wagoid/commitlint-github-action action to v6
• fix(deps): update dependency dotenv to v16
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency eslint-plugin-jest to v25.7.0
• chore(deps): update dependency eslint-plugin-unicorn to v40.1.0

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update babel monorepo (@babel/core, @babel/preset-env, @babel/preset-typescript)
• chore(deps): update commitlint monorepo (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency esbuild to v0.20.2
• chore(deps): update dependency eslint to v8.57.0
• chore(deps): update dependency eslint-plugin-import to v2.29.1
• chore(deps): update dependency typescript to v4.9.5
• chore(deps): update jest monorepo (@types/jest, babel-jest, jest)
• chore(deps): update typescript-eslint monorepo to v5.62.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

I want to optionally pass in --name example email [email protected] instead of filling out the interactive answers.

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

npm install babel-plugin-macros --save-dev

And then in babel config:

plugins: [
    "macros",
]

Bug report

Markdown files that aren't staged are linted within lint-staged.

Steps to reproduce

1. Add a markdown file that fails linting
2. Git stage a different markdown file that passes linting
3. Run lint-staged

Expected behavior

Lint-staged should be successful.

Actual behaviour

Lint-staged lints the other file.

Environment

• create-exposed-app version: latest
• Node.js version: 10.1.0
• npm version: 6.4.1

Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate bug reports.
• Title is a summary of the bug report, in present tense, and ideally < 50 characters

✨ Enhancement Request

Currently files are overwritten without warning. This can be dangerous, especially for those without version control.

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters
• Ready for review

✨ Enhancement Request

Currently only code contributors are recognised, and only by a very small link the README file.

Implement the all-contributors table: https://github.com/all-contributors/all-contributors

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters
• Ready for review

✨ Enhancement Request

An 'active: yes' badge can actually become out of date, whereas a 'last commit' badge will always be true.

https://shields.io/category/activity

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters
• Ready for review

It's outta date!

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Logging is common for every app, and having these provided will save time.

Ideally with tests.

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

It is easy for commits to appear in master that do not follow conventional commits, and then break the automated release process.

Example: https://github.com/seek-oss/commitlint-config-seek

Note: this only needs to apply in the master branch. Other branches can follow any commit messages they like. When they are squashed + merged, the commit should then follow conventional commits.

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

I think this should work:

roots: ["<rootDir>/src/"]

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Add test coverage reporting tool, e.g. https://coveralls.io/

What other tools exist?

There are many dependencies which are no longer required, or should be moved to devDependencies instead.

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

✨ Enhancement Request

it would be useful to browse an example app, to see how create-exposed-app is pieced together.

It could be run before being published and stored in an examples directory.

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters
• Ready for review

Bug report

Running npm run dev searches for missing file

Steps to reproduce

Run npm run dev

Expected behavior

The command should run successfully.

Actual behaviour

Searching for missing src/create-exposed-app.ts file.

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Currently the test script generates a coverage report. However this is quite slow, and is better off to be run only when required. Recommend adding a test:coverage command.

{
  "test": "jest --passWithNoTests",
  "test:coverage": "jest --passWithNoTests --coverage",
}

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Currently with dev and dev:onchange command, the scripts get confusing if adding other dev:* commands (e.g. "dev:debug": "DEBUG=1 npm run dev") (FYI - might be useful to add this, too!)

Recommended to rename to something like:

{
    "build-serve": "babel-node --extensions .js,.jsx,.ts,.tsx src/course-directory-api.ts --inspect",
    "build-serve:watch": "nodemon --ext js,jsx,ts,tsx --delay 1 --exec npm run build-serve",
    "dev": "NODE_ENV=development npm run build-serve:watch",
    "dev:debug": "DEBUG=1 npm run dev",
}

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Prefer an ESLint plugin, if it exists.

If not, I know there is a separate markdown linting tool.

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

I believe package.json should be human readable. Currently the URLs are pushed too high on the page, when it's more common scan for version numbers and dependencies.

Default options: https://github.com/cameronhunter/prettier-package-json/blob/master/src/defaultOptions.js

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

It is annoying to re-type the project package name when re-syncing with create-exposed-app.

Default the answer to the name of the directory.

🐛 Bug report

As I go through the getting started, and run the npm init exposed-app, my terminal gets stuck after the new 'hello-world' git branch is checked out.

Steps to reproduce

1. Install create-exposed-app on a Windows 7 machine
2. Run npm init exposed-app

Please include if possible and/or relevant: code, config, links, repository that reproduces the bug.

Expected behavior

Installation should progress to 'Copying 50 files' as per the gif shows on the Read me.

Actual behaviour

No error message is logged, and the Terminal session keeps hangin.

Environment

• create-exposed-app version: latest
• Node.js version: v10.13.0
• npm version: 6.4.1
• Operating System and version: Windows 7
• Device used: N/A
• Browser name and version: N/A

Additional

No ideas.

✅ Checklist

• Following CODE_OF_CONDUCT.md
• Checked for duplicate bug reports
• Title is a summary of the bug report, in present tense, and ideally < 50 characters
• Ready for review

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

This is useful for every project I know of.

Notes:

• Include item in .gitignore file
• Include .env.example file (is this the convention?)
• Include items in documentation for developers to alter the .env file
• Import manually within source files, or force the import via CLI scripts?

🐛 Bug report

Not all markdown files are linted when running npm run lint:markdown.

Steps to reproduce

1. Create a markdown file that fails linting in .github directory
2. `npm run lint:markdown"

Expected behavior

Linting should fail

Actual behaviour

Linting is successful

Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate bug reports.
• Title is a summary of the bug report, in present tense, and ideally < 50 characters

🐛 Bug report

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate bug reports.
• Title is a summary of the bug report, in present tense, and ideally < 50 characters
• Ready for review

✨ Enhancement Request

Running npm run dev should simply compile files.

Currently the npm run dev command is also building DTS files, which runs type checking. If something breaks type checking, the build shows a failure.

This is not ideal. Type checking should be a separate process manually run after development, along with linting and testing. Having type checking errors during development breaks the flow.

✅ Checklist

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters
• Ready for review

• Following CODE_OF_CONDUCT.md.
• Checked for duplicate enhancements.
• Title is a summary of the enhancement request, in present tense, and ideally < 50 characters

Enhancement

Example:

[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com)

There are many many more.