The capture includes JS, so this should work for most JS-dependent sites, with the exception of scripts loading other additional assets.
Tbh, often those are superfluous, or egregious examples of bad web dev, so it seems a reasonable solution for most cases.
SingleFile is a different approach, but it's a lot more involved/less convenient than a cli, and loading in something like WebDriver on the cli for this would be overkill, unless you're doing very serious archival work.
superfluous, or egregious examples of bad web dev??
Do you know what Web 2.0 is? Do you know what are React, Angular, and the other JS Frameworks?
When you create a modern webapp, a lot of data are retrieved from servers as Json and formated in the browser in Javascript. Even sometimes Css is generated on browser-side. Even more, on webapp where user login is taken into account, the display is modified accordingly.
That's the web of 2019. The approach consisting of geting remote files and launching them in a browser is really naive.
Speaking of SingleFile, it as a cli version and can handle full web 2.0 webapp without any problem. And of course, the Web 1.0 webapps work as well.
With the exception of actual XHR requests (which should ideally be for dynamic resources, and as such somewhat outside the remit of saving a webpage), I was referring specifically to JS loading JS, etc. solutions. React, Angular do not recommend/advise you to do this. This isn't a requirement in Web 2.0 or Web 5.0 or anything else.
In terms of React at least, fetch requests are not a part of the framework in any way and any present would typically be done in custom code in lifecycle methods. Even Redux, is—by default—client-side only. Stores are in-memory, actions populating them would make fetch requests with React/Redux-independent logic.
Other JS frameworks are, typically, the same. And all of that is just considering dynamic XHR. Loading scripts is much less typical, and never required. The most common application of this I've seen is the GA snippet, which mainly does it to ensure the load is async without relying on developer implementation: it's 100% unnecessary to do it this way.
So yes, unless you're distributing a tracking snippet that you expect non-devs to be blindly pasting into their wordpress panels and still have it work efficiently, generally speaking use of this method is never necessary, and commonly a red flag for poor architecture.
I think that's exactly what that person means by superfluous and egregious examples of bad web development; SPAs, javascript frameworks of that nature. :p
Yes, the debate between building a SPA with rich features or Web old pages with good SEO is eternal :)
We see more and more an hybrid approach that can be called web 1.5 :)
Ajax will* still work fine with an internet connection as long as those ajax endpoints don't require cookies and don't linkrot.
* not 100% sure how the tool handles relative URLs embedded in source : if it's not clever enough though, this is very fixable via PR (as in its not an architectural limitation)
The main problem with too many websites is they've become too much about technology and have left visitors, as well as the spirit and intent of the internet behind.
By default, it will capture everything that would be interpreted/displayed. However, you can also run it with Selenium (and Firefox) instead of Puppeteer, and install your favorite extensions to block all the unwanted resources (there's a switch for that).
Yes, It's like Firebase with more turnkeys services, serverless capabilities, and with the ability to host it anywhere.
Can you send me a mail for financial requests ?
morvan (at) zetapush (dot) com
When you need to create a Web or mobile application, you have to create your backend, you must set up servers, set up databases (or possibly take them to a hosting company) and you must code your server code.
To do this, you need to hire an architect, a backend developer and for your web or mobile application, Fronts developers. It's very complex, it takes time and developer costs are high.
ZetaPush offers turnkey services that are instantly deployed on ZetaPush infrastructure. A front developer is autonomous, he does not need to have knowledge of software architecture or backend: only JavaScript. One developer versus at least three! It makes the difference!
In short, ZetaPush saves companies a lot of time and money when they choose us.
If you want to move to an other BaaS, ZetaPush provides NoSQL as a service, File storage as a service, Search as a service and lot's of other things for mobile, web, server and IoT
Hi,
at zetapush (http://zetapush.com), we provide a realtime BaaS with database, file storage, search engine, ... everything with a websocket connection.
You can use our javascript SDK to connect to our clusters.
