superplate
lighthouse-ci
superplate | lighthouse-ci | |
---|---|---|
32 | 18 | |
2,760 | 6,278 | |
0.5% | 0.8% | |
6.9 | 7.1 | |
3 months ago | 5 days ago | |
TypeScript | JavaScript | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
superplate
- Faster way to kickstart and develop backend REST apis?
-
Superplate - FRONTEND BOILERPLATE
To learn on how superplate and its plugins work, you can check out our documentation.
- We built an Open Source Next.js and React project starter with +30 plugins
-
5 Best Free Platforms for Hosting Hobby Web Projects
You can create a simple Refine application using superplate. It is a handy tool for creating production-ready React projects quickly.
- A well-structured production-ready frontend boilerplate with Typescript, React Testing Library, styled-component, React Query, .env, Axios, Bundle Analyzer, Prettier and 30+ plugins. superplate creates projects for React.js, Next.js, and refine.
- Superplate - An Open Source Next.js and React boilerplate with +30 plugins
-
Next.js and React Project Starter CLI with 30+ Plugins
💫GitHub Repo: https://github.com/pankod/superplate
- We built CLI for bootstrapping Next.js boilerplate with +30 plugins
lighthouse-ci
-
help needed with lighthouse ci for angular, github actions, PROTOCOL_TIMEOUT: (Method: Debugger.disable)
- referred to https://github.com/GoogleChrome/lighthouse/issues/6512 but didnt see network.disable error - added staticdistdir as per https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/configuration.md,
-
Continuous performance audits in Nuxt with Lighthouse CI and Github Actions
This approach would suit most of the cases however to achieve more accurate performance audits you should be conducting Lighthouse tests on a dedicated server to avoid results being affected by the machine capabilities. In other words, if you are running Lighthouse audits on a repository where there are several pull requests/workflows/pushes going on, the result of this audit may not be accurate and this is what we want to avoid. For that you would need a separate machine with Lighthouse Server installed on it. So on a pull request you would trigger this machine to conduct a performance audit and return response to your repository.
-
Measuring Page Speed with Lighthouse
And finally, Lighthouse has a CI version you can run in your continuous integration. We’ll use this method to schedule periodical benchmarks.
-
Ensure your Next.js app's performance is top-notch with Lighthouse CI and GitHub Actions
TLDR; I use the Google Chrome Lighthouse CI with a .lighthouserc json configuration to test next start. The Lighthouse CI GitHub app is used to return a pass or fail status check in a PR.
-
Everything you need to know about Web Performance (in 5 Minutes)
You should also incorporate performance checks into your CI/CD pipeline. Use Lighthouse CI to run a synthetic Lighthouse test on each PR (PS: Learn why you shouldn't believe the Lighthouse score alone) and bundlesize package to raise alerts if your bundle size exceeds a certain threshold. For more nuanced data you should use WebPageTest.
-
Accessibility Automation tool for CI pipeline
You can also run Google’s Lighthouse CI tool against multiple URLs, and then hook that up to their self-hosted dashboard service: https://github.com/GoogleChrome/lighthouse-ci
-
Understanding SEO and Web Vitals for your NextJS site and how to improve them?
You can also set up lighthouse-ci as a github action to evaluate the web vitals on push or in pull requests.
-
You’re probably using Lighthouse wrong: How we got tricked by a single magic number
You can have more consistent results if you set up Lighthouse CI in an external environment to test your page or use tools like SpeedCurve, but if you need to quickly inspect a website, I suggest taking a look at Page Speed Insights.
-
Frontend Testing: No more Unit/Integration/E2E categorizations and priorities
This name is already self-explanatory, and developers just need to run Lighthouse or its CI.
-
I built an open-source tool that scans your entire website with Google Lighthouse (unlighthouse.dev)
They also have a powerful CI tool (https://github.com/GoogleChrome/lighthouse-ci) with custom timelines, may look to implement it at some point
What are some alternatives?
next-boilerplate - A well-structured production ready Next.js boilerplate with Typescript, Redux, Jest, Enzyme, Express.js, Sass, Css, EnvConfig, Fetch, Reverse Proxy, Bundle Analyzer and Built-in Project CLI. https://pankod.github.io/next-boilerplate/
pa11y - Pa11y is your automated accessibility testing pal
create-next-stack - Create Next Stack is a website and CLI tool used to easily set up the boilerplate of new Next.js apps.
WebdriverIO - Next-gen browser and mobile automation test framework for Node.js
Refine - A React Framework for building internal tools, admin panels, dashboards & B2B apps with unmatched flexibility.
lighthouse - Automated auditing, performance metrics, and best practices for the web.
refine - Build your React-based CRUD applications, without constraints. [Moved to: https://github.com/refinedev/refine]
nightwatch - Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack
vite-electron-builder - Secure boilerplate for Electron app based on Vite. TypeScript + Vue/React/Angular/Svelte/Vanilla
WebPageTest.api-nodejs - WebPageTest API wrapper for NodeJS
pathpida - TypeScript friendly internal link client for Next.js, Nuxt.js and Sapper.
pa11y-ci - Pa11y CI is a CI-centric accessibility test runner, built using Pa11y