{"action":"created","issue":{"url":"https://api.github.com/repos/nozzle/react-static/issues/371","repository_url":"https://api.github.com/repos/nozzle/react-static","labels_url":"https://api.github.com/repos/nozzle/react-static/issues/371/labels{/name}","comments_url":"https://api.github.com/repos/nozzle/react-static/issues/371/comments","events_url":"https://api.github.com/repos/nozzle/react-static/issues/371/events","html_url":"https://github.com/nozzle/react-static/issues/371","id":296578361,"number":371,"title":"Large builds, routeInfo.js","user":{"login":"fmujakitz","id":17797495,"avatar_url":"https://avatars0.githubusercontent.com/u/17797495?v=4","gravatar_id":"","url":"https://api.github.com/users/fmujakitz","html_url":"https://github.com/fmujakitz","followers_url":"https://api.github.com/users/fmujakitz/followers","following_url":"https://api.github.com/users/fmujakitz/following{/other_user}","gists_url":"https://api.github.com/users/fmujakitz/gists{/gist_id}","starred_url":"https://api.github.com/users/fmujakitz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fmujakitz/subscriptions","organizations_url":"https://api.github.com/users/fmujakitz/orgs","repos_url":"https://api.github.com/users/fmujakitz/repos","events_url":"https://api.github.com/users/fmujakitz/events{/privacy}","received_events_url":"https://api.github.com/users/fmujakitz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-02-13T00:58:14Z","updated_at":"2018-02-13T17:40:05Z","closed_at":null,"author_association":"NONE","body":"Build that contains 100k+ pages creates significantly large routeInfo.js, which contains entries for every registered route.\r\n\r\nIs there any way to overcome this obstacle?\r\n\r\nBtw, really cool lib. Kudos!"},"comment":{"url":"https://api.github.com/repos/nozzle/react-static/issues/comments/365344515","html_url":"https://github.com/nozzle/react-static/issues/371#issuecomment-365344515","issue_url":"https://api.github.com/repos/nozzle/react-static/issues/371","id":365344515,"user":{"login":"tannerlinsley","id":5580297,"avatar_url":"https://avatars0.githubusercontent.com/u/5580297?v=4","gravatar_id":"","url":"https://api.github.com/users/tannerlinsley","html_url":"https://github.com/tannerlinsley","followers_url":"https://api.github.com/users/tannerlinsley/followers","following_url":"https://api.github.com/users/tannerlinsley/following{/other_user}","gists_url":"https://api.github.com/users/tannerlinsley/gists{/gist_id}","starred_url":"https://api.github.com/users/tannerlinsley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tannerlinsley/subscriptions","organizations_url":"https://api.github.com/users/tannerlinsley/orgs","repos_url":"https://api.github.com/users/tannerlinsley/repos","events_url":"https://api.github.com/users/tannerlinsley/events{/privacy}","received_events_url":"https://api.github.com/users/tannerlinsley/received_events","type":"User","site_admin":false},"created_at":"2018-02-13T17:40:05Z","updated_at":"2018-02-13T17:40:05Z","author_association":"COLLABORATOR","body":"A few things: \r\n- The route info file contains a list of all statically-generated routes\r\n- It also contains each routes corresponding hashes for retrieving the least amount of data as possible to displaying it.\r\n- This data needs to be fetched before *any* subsequent navigation can happen after the first load, so we can know what data we need t load for the route.\r\n\r\nHere's an idea. I'm not sure it will work, but it's a good brain-storming start.  We could these route hashes in a file per route, in separate directory at the root called `__routes` So the route hashes for the `blog/post-1` path would live at `/__routes/blog/post-1`. And it would contain the hashes for each data file it needs to fetch to display that path.\r\n\r\nThe benefit to this would be that there is no `routeInfo.js` file to download for each session, thus very large sites would work well.\r\n\r\nThe downside to this is there would be added latency to download the specific path's routeInfo file, then finally requesting the assets. Whereas currently, the assets can be fetched immediately when a new path is being navigated to."}}
{"actor":{"display_login":"tannerlinsley"}}