Thedcd-order-app NPM

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

`npm start`

Runs the app in the development mode. Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits. You will also see any lint errors in the console.

`npm test`

Launches the test runner in the interactive watch mode. See the section about running tests for more information.

`npm run build`

Builds the app for production to the build folder. It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes. Your app is ready to be deployed!

See the section about deployment for more information.

`npm run eject`

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Linking and Unlinking in Development Environments

As a Micro Front End, developers may want to link this application to another project in their development environment prior to publishing to a private or public NPM registry. The following steps describe how to link this application to another project within a development environment. Please see https://dev.to/erinbush/npm-linking-and-unlinking-2h1g for reference.

To Link:

Navigate to the package directory.
Run the npm link command to create a global link.
Navigate to the project directory where you will install the package after its been published.
Run the npm link <name of package to be linked> command to link the package to the project.

To Unlink:

Navigate to the project directory where the package has been linked.
Run the npm unlink --no-save <name of package that was linked> command to unlink the package from the project.
Navigate to the package directory.
Run the npm unlink command to remove the global link.

Publish package to NPM

As a Micro Front End, this application may be published to a private or public NPM registry. The following steps describe how to publish to public NPM registry. If you already have an NPM account then proceed. If not, please create an account at: https://www.npmjs.com/

Run the npm login command and provide your username and password (This cmd doesn't work well with Visual Code's integrated Bash terminal. I suggest using a Git Bash cmd prompt).
Run the npm run publish:npm command to transpile the project. (Integrating with npm run build instead of this script requires some investigating)
Run the npm publish command to publish the package.
Run the npm install <name of package to be installed> command while in the project directory of a different project to install the package into that project.

Publish a new version of an existing NPM package

Change the version in the package.json according to semantic versioning specs at: https://docs.npmjs.com/about-semantic-versioning.
Run the npm login command and provide your username and password (This cmd doesn't work well with Visual Code's integrated Bash terminal. I suggest using a Git Bash cmd prompt).
Run the npm run publish:npm command to transpile the project. (Integrating with npm run build instead of this script requires some investigating)
Run the npm publish command to publish the package.
Run the npm install <name of package to be installed> command while in the project directory of a different project to install the package into that project.