Search Results for "js framework"

Effortlessly build high-performance & high-quality Vue.js 3 user interfaces in record time. Combine the power of Quasar UI with Quasar CLI. One source code for all platforms simultaneously with all the latest and greatest best practices out of the box. Focus only on your app's features and forget about the boilerplate around it. Build high-performance VueJS user interfaces in record time: responsive Single Page Apps, SSR Apps, PWAs, Browser extensions, Hybrid Mobile Apps and Electron Apps....

TARS is a builder for the modern frontend of any complexity, which is based on Gulp.js. It facilitates and accelerates the process of web development. TARS will be suitable for teams and individual developers. It solves the most routine cases associated with web development and brings you more pleasure from work. TARS is a framework for gulp, including a set of gulp-tasks. It allows for easy expansion (creating new tasks) and customization (modification of existing tasks), provides a...

Tweak the create-react-app webpack config(s) without using 'eject' and without creating a fork of the react-scripts. All the benefits of create-react-app without the limitations of "no config". You can add plugins, loaders whatever you need. As of Create React App 2.0 this repo is "lightly" maintained mostly by the community at this point. Use next.js or Razzle which both support custom Webpack out of the box. You can try customize-cra for a set of CRA 2.0 compatible rewirers, or any of the...

PWA is a “universal, framework-agnostic PWA builder” developed by Luke Edwards (lukeed) that aims to let developers scaffold progressive web apps with minimal friction across different view frameworks or libraries. Unlike many CLI tools that target a specific framework (React, Vue, Svelte), this project intentionally tries to remain agnostic, supporting presets for Preact, React, Vue, Svelte and even vanilla JS, while offering all the PWA boilerplate you need (service workers, manifest, offline support) right out of the box. ...

The gap between performance and experience has always been the primary reason for mobile app developers to abandon HTML5. The browser’s natural page-cutting white screen, the unbearable turning animation, the jittering of floating elements, and the inability to pull down to refresh smoothly, all of which frustrate HTML5 developers, especially when they get a low-end Android machine to run, and the phone falls. On the other hand, the browser default control styles are few and ugly, making a...