Add documentation to demonstrate code splitting on server side apps.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
This is with reference to this link. Though i admit the documentation is pretty lucid, i feel a section can also be made for code splitting with server sided react apps. This is particularly tricky as correct bundles have to be utilised / picked up on both server and client side. This will be particularly useful for someone who is not using next / gatsby and is trying to use their own webpack config. Alternatively we can also show the above using react-loadable. I know the docs here are pertaining to just react, but adding this section may be helpful. If okay i'm cool with submitting a PR.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with content/docs/code-splitting.md, then review the issue's server-side React and custom webpack configuration scenario. Decide whether the documentation should cover custom server/client bundle selection or demonstrate react-loadable. Done means the docs clearly explain server-side code splitting for apps not using Next or Gatsby.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, webpack
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100