chore: replace create-react-app with vite (#9)

gregjopa · Jul 10, 2023 · add36d1 · add36d1
1 parent b79e598
commit add36d1
Show file tree

Hide file tree

Showing 20 changed files with 7,926 additions and 26,045 deletions.
diff --git a/.eslintrc.js b/.eslintrc.js
@@ -0,0 +1,24 @@
+module.exports = {
+ env: {
+ browser: true,
+ es2021: true,
+ },
+ extends: [
+ "eslint:recommended",
+ "plugin:react/recommended",
+ "plugin:@typescript-eslint/recommended",
+ ],
+ overrides: [],
+ parser: "@typescript-eslint/parser",
+ parserOptions: {
+ ecmaVersion: "latest",
+ sourceType: "module",
+ },
+ plugins: ["react", "@typescript-eslint"],
+ rules: {},
+ settings: {
+ react: {
+ version: "detect",
+ },
+ },
+};
diff --git a/.gitignore b/.gitignore
@@ -9,7 +9,7 @@
 /coverage
 
 # production
-/build
+/dist
 
 # misc
 .DS_Store

diff --git a/.prettierignore b/.prettierignore
@@ -1,2 +1,2 @@
-/build
+/dist
 /coverage
diff --git a/README.md b/README.md
@@ -1,9 +1,12 @@
+TEMP TODOS
+
+- update readme
+- fix prod deploy
+
 # Piano Flash Cards React App
 
 ![piano flash card app screenshot](images/piano-flash-cards-app-screenshot.jpg)
 
-This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
-
 ## Audio
 
 The piano sounds are provided by [Salamander Grand Piano](https://archive.org/details/SalamanderGrandPianoV3) under the Creative Commons license.
@@ -15,38 +18,19 @@ In the project directory, you can run:
 ### `npm start`
 
 Runs the app in the development mode.\
-Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
+Open [http://localhost:5173](http://localhost:5173) 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](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
+Launches the test runner in the interactive watch mode.
 
 ### `npm run build`
 
-Builds the app for production to the `build` folder.\
+Builds the app for production to the `dist` 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](https://facebook.github.io/create-react-app/docs/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](https://facebook.github.io/create-react-app/docs/getting-started).
-
-To learn React, check out the [React documentation](https://reactjs.org/).
diff --git a/public/index.html → index.html b/public/index.html → index.html
@@ -1,30 +1,21 @@
 <!DOCTYPE html>
 <html lang="en">
  <head>
- <meta charset="utf-8" />
- <link rel="icon" type="image/svg+xml" href="%PUBLIC_URL%/favicon.svg" />
- <link rel="icon" type="image/png" href="%PUBLIC_URL%/favicon.png" />
- <meta name="viewport" content="width=device-width, initial-scale=1" />
+ <meta charset="UTF-8" />
+ <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
+ <link rel="icon" type="image/png" href="/favicon.png" />
+ <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  <meta name="theme-color" content="#000000" />
  <meta
  name="description"
  content="Practice memorizing notes with these treble and bass clef flash cards"
  />
- <link rel="apple-touch-icon" href="%PUBLIC_URL%/logo192.png" />
+ <link rel="apple-touch-icon" href="/logo192.png" />
  <!--
  manifest.json provides metadata used when your web app is installed on a
  user's mobile device or desktop. See https://developers.google.com/web/fundamentals/web-app-manifest/
  -->
- <link rel="manifest" href="%PUBLIC_URL%/manifest.json" />
- <!--
- Notice the use of %PUBLIC_URL% in the tags above.
- It will be replaced with the URL of the `public` folder during the build.
- Only files inside the `public` folder can be referenced from the HTML.
-
- Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will
- work correctly both with client-side routing and a non-root public URL.
- Learn how to configure a non-root public URL by running `npm run build`.
- -->
+ <link rel="manifest" href="/manifest.json" />
  <title>Piano Flash Cards</title>
  </head>
  <body>
@@ -63,15 +54,6 @@
  };
  </script>
  <div id="root"></div>
- <!--
- This HTML file is a template.
- If you open it directly in the browser, you will see an empty page.
-
- You can add webfonts, meta tags, or analytics to this file.
- The build step will place the bundled scripts into the <body> tag.
-
- To begin the development, run `npm start` or `yarn start`.
- To create a production bundle, use `npm run build` or `yarn build`.
- -->
+ <script type="module" src="/src/index.tsx"></script>
  </body>
 </html>