A light weight interface to obtain weather forecast information

1. GitHub Respository
2. Changelog
3. Trello Board
4. Deployed App

1. JavaScript
2. Node.js v.20+
3. Git
4. release-please
5. commitlint
6. BabelJS
7. [ESLint] (https://eslint.org/)
8. Webpack 5
9. React 18
10. @svgr/webpack

1. From your command line shell (Bash or Zsh), in a directory of your choice, enter the following command, to create a folder called "andy-client": git clone https://github.com/wingedearth/andy-client.git
2. Enter cd andy-client to enter the folder.
3. Enter yarn to run yarn, which will install the local NPM package dependencies. If you do not have yarn installed globally on your machine, then first enter npm i -g yarn to install yarn.

1. Enter yarn build:dev on the command line to build/transpile application with Webpack watch mode.
2. Enter yarn dev on the command line (in a different tab) to start application.

1. Enter yarn start to build and start the server

When the server is available, use the /version endpoint to see app information.

From conventionalcommits.org:

The commit message should be structured as follows:

[optional scope]:

[optional body]

[optional footer(s)] The commit contains the following structural elements, to communicate intent to the consumers of your library:

fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning). feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning). BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type. types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others. footers other than BREAKING CHANGE: may be provided and follow a convention similar to git trailer format.

Merging code to the master branch will auto generate or update a Release PR. When ready to bump the application version, simply merge the Release PR in GitHub. This will also update the changelog.