Chatbot TestA helper project for developing and testing the chatbot framework.
This is the "quick and dirty" workflow we are following:
- Clone this repo and the chatbot repo as siblings
- The chatbot library code lives in src/lib/src. Make changes to stuff in here as you wish. Remember that whatever you want built must end up in src/lib/src/engine/index.ts or src/lib/src/components/index.ts.
- See impact immediately by hot-reloading this "test" app. This is much faster than writing the chatbot code independently, building each time and linking via
- When you want to build and release the chatbot library itself, open it up and run
yarn build. This will copy over the contents of src/lib/src into /src, and build.
- Make sure you that manually update /package.json to reflect any dependency changes you have made in the package.json file here!
- To build chatbot-engine (the extraction of the core engine from chatbot), clone the chatbot-engine repo as a sibling as well, and run the above two steps in it.
Publishing to npmWe use a tool called np.
- Install np:
npm install --global np
- Run np and follow its instructions:
np --no-tests(without the
--no-testsflag, the deployment seems to get stuck at the tests step)
This project was bootstrapped with Create React App.
Available ScriptsIn the project directory, you can run:
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.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the
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.
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
ejectat 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
ejectwill 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 MoreYou can learn more in the Create React App documentation.
To learn React, check out the React documentation.