This project kicks the tires on TypeScript with React.
This was created using npx create-react-app ts-test --typescript.
It uses json-server as a mock API.
I used the following resources to build this:
- Microsoft TS Handbook
- Compiler / TSConfig options
- react-typescript-samples project
- TS tips
- Interface vs Type
- Ultimate React Component Patterns and Medium Post
- Multiple TS Config
- Express TS example
- Use TS Import() to import types (the rest of the file isn't pulled into your app, so a perf win if the file with types has runtime code your app doesn't use. Note that TypeScript is smart enough to remove imports that only use types.)
- TS Conversion Guide - Same app written in JS and TS from Microsoft
- TS with Redux
This project was bootstrapped with Create React App.
In TypeScript, two types are compatible if their internal structure is compatible.
& - Intersection operator (create a new type by intersecting one or more types or interfaces)
Partial<Shape & Perimeter> - Partial mapped type
- Can't use
implementson class with a union type - Can't use
extendson interface with a union type - Declaration merging doesn't work with type. So use interface for public API definition when authoring a library or 3rd party ambient type definitions. Why? Interfaces can be merged (you can declare the same interface twice). Types don't support that.
In 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 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.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.