vini-test v0.0.37

Getting Started with Create React App

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

yarn 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.

yarn test

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

yarn 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.

yarn 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.

Publishing/Linking Locally

In order to get both projects linked and work on it locally, first you need to install YALC globally.

yarn global add yalc

Then, to start working and have the build automatically created and published locally run:

yarn dev

That will watch for changes, build a new version, replace paths and publish locally on yalc.

To link this package in BOLT, run command;

yalc add first-onsite-inventory

The BOLT webapp will automatically update when changes are done in the module and published locally, sometimes a manual update is needed after changes are compiled, stop yarn dev running in BOLT and;

yalc update this goes on parent project folder (BOLT/Jarvis)

Yalc documentation

yarn updateJarvisCode

That command will copy the needed dependencies from BOLT into this project, it has to be executed when we need to update the BOLT dependencies, after we pull the latest changes from BOLT. Let the team know if you are updating BOLT dependencies to avoid conflicts (if more than one dev updates them, the one merging last will have conflicts).

Publishing NPM Package

Development NPM Package

First you have to go to package.json:

• check if the name of the module is correct, we are using "vini-test" for development purposes but the official name should be "first-onsite-inventory"(we are not publishing with the correct name yet b/c once we do that there's no turning back)
• increase version number
• if you want to publish it to the "vini-test" package, change the private property to false

Save package.json changes and wait for it to finish building.

After it's all set, open a terminal from the module folder.

• use npm login to provide npm credentials (for "vini-test" you can reach out to @vinicius.alves)
• use npm publish to finally publish the new module version