fullstack-cra-app-template v0.0.6

Fullstack CRA(create-react-app) Application Template

A CRA-based template that can customize webpack configuration and node.js scripts.

This is a React application created using create-react-app 5+, which can configure webpack independently and use Node.js scripts to export a .zip package.

This template enhances the scripts from package.json, without breaking the structure of CRA itself. It is used to remove the external React and ReactDOM libraries so that the bundles are completely separated from the React vendor.

File Structures

fullstack-cra-app-template/
├── README.md
├── LICENSE
├── tsconfig.json
├── custom.webpack.config.js
├── package-lock.json
├── package.json
├── my-package/<your_package_name>.zip
├── scripts/
├── public/
├── src/
│   ├── index.tsx
│   └── ...
└──

Getting Started

Make sure if NODEJS is installed on your computer.

Install Dependencies:

$ npm install

It will create node_module folder in this all dependency files will be install with this command.

Development And Debugging:

$ npm run start

Production Build :

$ npm run build 

Export to zip file

♥️ It will automatically generate a compressed package <your_package_name>.zip with the same name as your current repository, and put it in the my-package folder, you can modifyThenameproperty in package.json configures this name

$ npm run export

Even More

For related operation commands, please refer to create-react-app

⚙️ Custom Configuration of Build

Excluding dependencies from the output bundles, you could change the package.json like this:

The buildConfig property will be linked to the Webpack configuration.

{
    ...
    "buildConfig": {
        "externals": {
            "react": "React",
            "react-dom": "ReactDOM"
        }
    },
    ...
}

If you want to cancel the external files setting, please change it to:

{
    ...
    "buildConfig": {
        "externals": ""
    },
    ...
}

⚠️ Installation Error or Unable To Run:

a) Has node_modules folder, just do it directly.

If running npm run <script> fails because Node has been upgraded, use npx -p node@<version> <your_script> to run:

such as

$ npx -p node@15.14.0 npm run dev
$ npx -p node@14.21.3 npm run start

b) If there is no node_modules folder, using npm install --legacy-peer-deps is still unsuccessful. After deleting the dependencies of package.json and remove file package-lock.json, use the following command to reinstall:

$ npm install <package1> <package2> --legacy-peer-deps
$ npm install --save-dev <package1> <package2> --legacy-peer-deps

c) NPM or NPX cache error

View the location of the local npm cache:

$ npm config get cache

Clear cache (npm and npx)

$ npm cache clean --force

or

$ rm -rf ~/.npm

Check cache

$ npm cache verify

Supported development environment

• create-react-app 5.x.x+

Licensing

Licensed under the MIT.