Search Results for "chrome os disk"

Nativefier is a command-line tool designed to create a desktop app for any web site with minimal configuration. Apps are wrapped by Electron (using Chromium under the hood) in an OS executable (.app, .exe, etc) for use on Windows, macOS and Linux. Nativefier will try to determine the app name, and well as lots of other options. If desired, these options can be overwritten. For example, to override the name, nativefier --name 'My Medium App' 'medium.com' Read the API documentation or run...

TagSpaces is a free, no vendor lock-in, open source application for organizing, annotating and managing local files with the help of tags. It features advanced note taking functionalities and some capabilities of to-do apps. The application is available for Windows, Linux, Mac OS and Android. We provide a web clipper extension for Firefox, Edge and Chrome for easy collecting of online content in the form of local files. File and folder management - TagSpaces provides a convenient user interface...

..., Progressive Apps are not supported everywhere, but we have added support for Safari & Chrome so your application can work as standalone applications when added to the home screen or saved as a desktop app. The very difficulty faced when developing enterprise applications is code splitting. We don't need everything in a single JS file. Why not create individual JS files for each respective module/page! We make it really easy here to just create a page that returns an array of routes.

This is a Neovim frontend built on Electron. The Neovim editor is composed as a Web Component and users can extend the UI with reusable Web Components, HTML, CSS and JavaScript. NyaoVim is built in the same spirit. NyaoVim contains the Neovim editor as a Web Component and extends its UI with web technology, as in other modern editors and IDEs (e.g. Atom, VS Code, LightTable). NyaoVim bundles no extended UI by default. It only provides the nice UI plugin architecture. Users can compose their...

A dead simple library to screenshot test React components. Under the hood, we start a local server that renders components server-side. Each component is given its own dedicated page (e.g. /render/my-component). Then we use Puppeteer to take a screenshot of that page. If you work on a team where developers use a different OS (e.g. Mac OS and Linux), or if you develop on Mac OS but use Linux for continuous integration, you would quickly run into issues where screenshots are inconsistent across...