portfolio-react VS loadable-components

Compare portfolio-react vs loadable-components and see what are their differences.

Our great sponsors
  • Amplication - open-source Node.js backend code generator
  • Appwrite - The open-source backend cloud platform
  • SurveyJS - A Non-Cloud Alternative to Google Forms that has it all.
  • Mergify - Updating dependencies is time-consuming.
  • Sonar - Write Clean JavaScript Code. Always.
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
portfolio-react loadable-components
2 12
146 7,327
- -
0.0 4.1
about 1 month ago about 1 month ago
JavaScript JavaScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of portfolio-react. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-13.


Posts with mentions or reviews of loadable-components. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-03.
  • 5 Small and Hidden React libraries you should already be using
    4 projects | dev.to | 3 Dec 2022
    And the best thing. It is really easy to use. Almost plug-and-play. So, give it a try! https://github.com/gregberge/loadable-components
  • How to use client-side only packages with SSR in Gatsby and Next.js
    2 projects | dev.to | 7 May 2022
    The library @loadable/component allows you to dynamically import components to your project, so they don't get rendered on the server. The following component uses leaflet, a library similar to google maps that only supports client-side rendering:
  • How to choose a third party package
    6 projects | dev.to | 4 Dec 2021
    It's very important that you are choosing an active project instead of a dead/unmaintained project. An active project improves over time through community feedback. An unmaintained project does not move forward, fix functional bugs or patch security issues. Sometimes, a very popular package can be abandoned and go into a "frozen" state with many open issues and pull requests. It might have been a great solution in the past, but this is a sign that we have to move on. An example is react-loadable. It was a great solution for a very long time for code-splitting in React. I totally loved it. But it's stale now with many issues and PRs since 2018 (this post is written at the end of 2021). Now, if I need to split code in React, I use loadable-components, which is in active development, becoming more popular, patches bugs reported by the community, and most importantly, solves my problems. My personal advice: choose a package that's active in the last 3-6 months, with issues that are being resolved and PRs that are being merged.
  • What are some issues with using React/Redux?
    6 projects | /r/reactjs | 30 Nov 2021
    Now client side rendering is very powerful and as I said in the first comment I'm two years in production of an app that's using things like lazy loading and client side routing and more to give the app a more regular application feel, but by using next.js to generate a static site my users would have benefited by not having to generate all the javascript their using on their own pcs.
  • Navigation in React App using React Router (v6)
    3 projects | dev.to | 9 Nov 2021
    When we have lot of pages in out application, we will end up having lot of code. We don't want our user to download all the code when they just load the home page. In order to package code of different routes to separate chunks, along with react router we can make use of loadable components, which takes advantage of dynamic imports.
  • Code Splitting in React using React.lazy and Loadable Components
    2 projects | dev.to | 19 Apr 2021
    In order to load the CatImage component to a separate bundle, we can make use of loadable components. Let's add @loadable-component to our package:
  • Priority loading in Reactjs
    2 projects | dev.to | 13 Feb 2021
    So by using Loadable components we can select the packages which we want to load after the content is loaded.
  • Lazy loading with React
    3 projects | dev.to | 16 Dec 2020
    Note: React.lazy and Suspense are not yet available for server-side rendering. If you want to do code-splitting in a server rendered app, React team recommends Loadable Components.

What are some alternatives?

When comparing portfolio-react and loadable-components you can also consider the following projects:

react-loadable - :hourglass_flowing_sand: A higher order component for loading components with promises.

react-router - Declarative routing for React

react-scroll - React scroll component

react-ssr-example - A simple React server-side rendering example with express and esbuild

Gatsby - The best React-based framework with performance, scalability and security built in.

electron-react-python-template - Multi-platform Electron template, using React & Redux Toolkit on the front-end and Python/Flask for microservices on the back-end.

lite-youtube-embed - A faster youtube embed.


react-async-component - Resolve components asynchronously, with support for code splitting and advanced server side rendering use cases.

strapi-template-portfolio - Template to create Strapi projects pre-configured for portfolio sites

react-portfolio - React Portfolio made with love ❤ from India