graphql-ssg
DISCONTINUED
stencil
Our great sponsors
| graphql-ssg | stencil | |
|---|---|---|
| 1 | 42 | |
| 31 | 11,340 | |
| - | 1.0% | |
| 6.7 | 9.2 | |
| over 1 year ago | 6 days ago | |
| TypeScript | TypeScript | |
| - | GNU General Public License v3.0 or later |
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.
graphql-ssg
We haven't tracked posts mentioning graphql-ssg yet.
Tracking mentions began in Dec 2020.
stencil
-
Web Components
Look into https://stenciljs.com/ .
We used https://stenciljs.com/ for web components to be consumed by angular, AEM and react at a previous employer. It uses tsx/jsx. Components are easy to write and it has good documentation.
-
Hexagonal architecture as a solution to the obsolescence of UI frameworks
For the creation of web components, even though writing in vanilla js is an option, we have chosen to do it via a dedicated framework, which will solve many potential integration/bundling problems. The choice of the framework will be made according to different factors that are not part of the scope of this article.
-
Ask HN: Help me pick a front-end framework
Maybe have a look at Stencil (+ Ionic). https://stenciljs.com/
Pro:
- Simple to learn
- Doesn't change all the time
- First-class TypeScript support
- Good default UI via Ionic
- Compiles to Web Components (although to be honest, this doesn't really matter)
- Easy testing
- Ionic as a company invests in Ionic the framework + Stencil the compiler. Might be around in 10 years, altough things could change. But this is true for all frameworks.
- You basically get an iOS/Android app for free, if you just dump the output in Capacitor (also developed by Ionic the company).
Cons:
- Stencil is not very widespread as a frontend framework.
-
A Letter to D1sc0rd for not Supporting the Linux Desktop
because react-native is only reactlike. I may or may not want to stick with that. I think something like this is leading us towards a better and less UI lib specific approach. https://github.com/ionic-team/stencil/ . I don't think is 100% where we end up, but it is based on web components, so it's moving the entire ecosystem forward, not just a slice of it.
-
By Crayons and For Crayons
The app is built using vanilla Web Components without using any component publishing libraries like Stencil, Lit and so on. The reason being I met with some roadblocks in building a drag-n-drop editor using these libraries. Actually the Crayons Team itself is using Stencil to build the Crayons components using TypeScript and React-like component semantics and finally publish them as platform native Web components and React wrappers for the same. You can find out more about this in the Stencil documentation.
-
Why we chose WebComponents for our Design System
Stencil
-
A Quick Guide to Mitosis: Why You Need It and How You Can Use It
This might sound very similar to the work the Ionic team did with Stencil. The one main difference is that we're not just outputting web components. Rather full framework-ready JavaScript. You can even compile the output to Stencil as well.
-
The Case for Web Components
While you can build components directly from the supporting Web APIs, you might find it productive to use a library that's been built to support this task. Lit and StencilJS are two of several libraries with acompanying tooling to help you build web components. And because they compile to the same 'target', they give you an additonal advantage: if you choose to switch web component libraries at some point in the future, you can make the switch for new components without having to rewrite the old ones, and use both in the same application.
-
What advantages does React have over Vue?
Web components, regardless of how they are written, work interoperably with each other on the page. Write them with - plain JavaScript, - a library like Lit, or - a full-on web components framework like Stencil. You can load each of them anywhere and use them separately or together wherever HTML and JavaScript work, which is everywhere. You can also use web components in old school frameworks. Why would you limit yourself to a closed silo when you can keep all the DX benefits of frameworks while producing more flexible components?
What are some alternatives?
lit - Lit is a simple library for building fast, lightweight web components.
Svelte - Cybernetically enhanced web apps
vite-ssg - Static site generation for Vue 3 on Vite
css-modules - Documentation about css-modules
shoelace-css - A collection of professionally designed, every day UI components built on Web standards. Works with all framework as well as regular HTML/CSS/JS. 🥾
turbo - The speed of a single-page web application without having to write any JavaScript
webcomponents - Web Components specifications
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
catalyst - Catalyst is a set of patterns and techniques for developing components within a complex application.
stencil-storybook-demo - This demo show how to run, build & deploy Storybook and Stencil from one repository
solid-site - Code that powers the SolidJS.com platform.
mitosis - Write components once, run everywhere. Compiles to Vue, React, Solid, Angular, Svelte, and more.