antonybudianto / create-react-app-express

⚙️ Express server for your Create React App (Backbone of cra-universal)

Welcome!

Hi, I'm Antony from Indonesia. I've 8+ years experience on web development from various industry (B2B, HRIS, E-Commerce, Fintech, CRM, Omni-channel).

I spent most of my time on Web development and also learned many other stacks along the journey to understand the whole picture better.

I also sometimes do open-source, and was Google Cloud Certified.

and lastly, Creator of Deesain and StickyNoted.

Some of notable professional achievements:

• Improved web service reliability and resilience by integrating custom PM2 with Systemd
• Initiated and supervise in-house SSR React Web Framework and support the migration
• Initiated autoscaling worker with custom consul DNS to save cost
• Initiated JavaScript Error Stack parser CLI to help FE team to pinpoint the error location without sourcemap
• Resolved long standing and high priority issue regarding FCM Notification token issue

Tech stacks:

• Frontend (React, Vue, Next.js, Nuxt)
• Backend (Java, Go, Rust)
• Infrastructure (Docker, Nginx)

Other online profile:

• Blog
• LinkedIn

---

create-react-app-express's Issues

Extend static-loader to configure the express static middleware

Usually I would want to set cache headers etc, so it seems like if static-loader abstracts away setting up the static routes, it should also accept additional configuration like the cache headers.
If you like I could look into a PR.

Remove lerna field

https://github.com/antonybudianto/create-react-app-express/blob/master/lerna.json#L2

lerna/lerna#1225

String renderer will be default on next major

CRA Express 2.0.0

New features:

• Loaders: functions that take express app instance and add the needed middleware / setup according to its usage.
  • Included basic loaders:
    • @cra-express/static-loader (for handling static assets)
    • @cra-express/universal-loader (for universal rendering)
      • this loader should be called last
  • If you use createReactAppExpress API, it used both loaders by default
  • Usecases / background:
    • useful when you want to build your own routes on top of create-react-app-express middleware. currently all routes are consumed by universal loader so it's not possible to create your own routes (e.g.: API routes, etc)
    • able to use universal rendering for existing/managed express app.
  • the naming can be confused with webpack loaders, any suggestions are welcome
• Babel bundling (for non-es6 compatibility)

Plan:

To make it more middleware oriented, than all-in-one magic API. Loaders are still considered magic though, but at least they only do one thing, unlike previous API.

• Forkable/custom loaders
  • Each loader will have their own package
  • The loaders source code will be still in this repo (mono-repo), will use Lerna
  • Developer will have more flexibility to fork and customize their own loader
  • Since loaders are just functions, you can write your own, publish, and replace the built-ins easily

Breaking changes:

• new package name: create-react-app-express -> @cra-express/{core, static-loader, universal-loader}
• createReactAppExpress() in on core, and it keeps the compatibility
• in short, you just need to update your package name and it should be okay

Pre-release

You can try by installing:

npm i @cra-express/[email protected]

⚠️ NOT FOR PRODUCTION USAGE

Final release is expected to be end if December