Skip to content

Latest commit

 

History

History
57 lines (33 loc) · 2.43 KB

README.md

File metadata and controls

57 lines (33 loc) · 2.43 KB
Raw

ChatGPT 2.0

ChatGPT 2.0 is a web-based chatbot application that utilizes OpenAI's GPT language model to provide answers to user questions and queries. The search results can be filtered and made exclusive by selecting the various models made available by OpenAI. This repository contains the source code for the application.

Technologies Used

The following technologies have been used in the development of ChatGPT 2.0:

  • Node.js with Express for the backend
  • React for the front-end
  • OpenAI GPT language model for the chatbot

Prerequisites

Before running the ChatGPT 2.0 application, ensure that the following are installed:

  • Node.js and NPM
  • A modern web browser
  • An OpenAI API key for using the GPT language model

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 your browser.

The page will reload when you make changes.
You may 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.