question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Discrepancies between SSR Example and Documentation

See original GitHub issue

💬 Questions and Help

Loadable Components project is young, but please before asking your question:

  • Read carefully the README of the project
  • Search if your answer has already been answered in old issues

After you can submit your question and we will be happy to help you!

Hi all, I am confused by the example for server-side-rendering.

In the example, there is both a nodeExtractor and a webExtractor. The nodeExtractor ends up using requireEntryPoints but webExtractor does not. Could someone explain to me the need for an extractor for node and a separate one for web? Furthermore, why does nodeExtractor utilize requireEntryPoints instead of specifying entrypoints in the constructor of ChunkExtractor?

Why are the above points also missing from the documentation?

Furthermore, I see a lot of specific changes to webpack.config.babel.js and babel.config.js that was not mentioned in the Documentation. What were the need for these changes in the example? Does the documentation need to be updated to reflect the same?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:10
  • Comments:11 (4 by maintainers)

github_iconTop GitHub Comments

6reactions
damassicommented, Feb 7, 2020

@imthinhvu - I’m running into the exact same problem you described. Mind sharing your solution?

5reactions
chronicIntrovertcommented, Mar 24, 2019

@neoziro - I laid out the differences when I opened the issue, can you please take a look if you haven’t yet? Primarily referencing need for nodeExtractor vs webExtractor, and use of requireEntrypoints – these are all part of the SSR example, but not in the documentation.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Client-side vs. Server-side vs. Pre-rendering for Web Apps
An SSR solution is something we used to do a lot, many years ago, but tend to forget in favor of a client-side...
Read more >
Client-Side vs Server-Side Rendering - Scythe Studio
The main difference between CSR and SSR is where the page is rendered. SSR renders the page on the server-side and CSR renders...
Read more >
What is server-side rendering and how does it improve site ...
Server-side rendering ensures that website content appears quickly, without first having to download and run application code.
Read more >
The Benefits of Server Side Rendering Over Client ... - Medium
The Theoretical Performance Benefit. Here is a very simple timeline diagram(super simple)to showcase the difference between SSR and CSR.
Read more >
Client Side (CSR) vs Server Side Rendering (SSR) - iteo
What are the performance differences between CSR and SSR? It depends but also, the type of rendering can influence many processes in the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found