Modern build setup with no configuration for [ React + TypeScript ] projects.
- Faster build times
- Namespaces support
- Module resolution support (baseUrl/paths)
- Type checking on a separate proccess
- Transpilation using ts-loader
- Provide compile-time information for styled components typescript-plugin-styled-components
Found any problem or bug? Please create a new issue || mailto : developer@nexbit.io
- Webpack 4
- up-to-date TypeScript
- Zero config optimize build
- TypeScript compilation ts-loader
- Type and tslint errors on a separate process fork-ts-checker-webpack-plugin
- Sass, Less and Css Modules css-modules
- Generate TypeScript typings for CSS modules typings-for-css-modules-loader
- Tranform SVG into React components svgr
- Use
.js|.jsx
and.ts|.tsx
files together.
Check out the template files for usage examples.
npx create-react-app my-app --scripts-version=@nexbit.io/react-scripts-ts
cd my-app/
yarn start
Install this package in yout project:
yarn add @nexbit.io/react-scripts-ts
Change your package.json configuration to use react-scripts-ts
{
"scripts": {
"start": "react-scripts-ts start",
"build": "react-scripts-ts build",
"test": "react-scripts-ts test --env=jsdom",
}
}
Ejecting is not supported in this project, you have 2 options:
-
Fork this project and create your own react-scripts-ts package.
-
Use react-app-rewired with custom scripts versions:
{
"scripts": {
"start": "react-app-rewired start --scripts-version @nexbit.io/react-scripts-ts",
"build": "react-app-rewired build --scripts-version @nexbit.io/react-scripts-ts",
"test": "react-app-rewired test --scripts-version @nexbit.io/react-scripts-ts --env=jsdom"
}
}
2018-2020 | NEXBIT.IO Ltd.