Alternatives to Stencil logo

Alternatives to Stencil

Svelte, React, Polymer, React Router, and styled-components are the most popular alternatives and competitors to Stencil.
47
58
+ 1
0

What is Stencil and what are its top alternatives?

Stencil combines some of the best features from traditional frameworks, but outputs 100% standards-compliant Custom Elements, part of the Web Component spec.
Stencil is a tool in the JavaScript Framework Components category of a tech stack.
Stencil is an open source tool with 9K GitHub stars and 572 GitHub forks. Here’s a link to Stencil's open source repository on GitHub

Top Alternatives to Stencil

  • Svelte

    Svelte

    If you've ever built a JavaScript application, the chances are you've encountered – or at least heard of – frameworks like React, Angular, Vue and Ractive. Like Svelte, these tools all share a goal of making it easy to build slick interactive user interfaces. Rather than interpreting your application code at run time, your app is converted into ideal JavaScript at build time. That means you don't pay the performance cost of the framework's abstractions, or incur a penalty when your app first loads. ...

  • React

    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • Polymer

    Polymer

    Polymer is a new type of library for the web, designed to leverage the existing browser infrastructure to provide the encapsulation and extendability currently only available in JS libraries. Polymer is based on a set of future technologies, including Shadow DOM, Custom Elements and Model Driven Views. Currently these technologies are implemented as polyfills or shims, but as browsers adopt these features natively, the platform code that drives Polymer evacipates, leaving only the value-adds. ...

  • React Router

    React Router

    React Router is a complete routing solution designed specifically for React.js. It painlessly synchronizes the components of your application with the URL, with first-class support for nesting, transitions, and server side rendering. ...

  • styled-components

    styled-components

    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅 ...

  • Angular CLI

    Angular CLI

    A command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications. You can use the tool directly in a command shell, or indirectly through an interactive UI such as Angular Console. ...

  • Ant Design

    Ant Design

    An enterprise-class UI design language and React-based implementation. Graceful UI components out of the box, base on React Component. A npm + webpack + babel + dora + dva development framework. ...

  • Angular Material

    Angular Material

    Sprint from Zero to App. Hit the ground running with comprehensive, modern UI components that work across the web, mobile and desktop. It allows to create material styled angular apps fast and easy. ...

Stencil alternatives & related posts

Svelte logo

Svelte

482
597
331
A UI framework that compiles into tiny standalone JavaScript modules
482
597
+ 1
331
PROS OF SVELTE
  • 33
    Performance
  • 27
    Reactivity
  • 26
    Javascript compiler (do that browsers don't have to)
  • 23
    Components
  • 21
    Real Reactivity
  • 21
    Lightweight
  • 20
    Simplicity
  • 19
    Fast as vanilajs
  • 17
    Near to no learning curve
  • 14
    Use existing js libraries
  • 14
    Compiler based
  • 13
    All in one
  • 12
    Scalable
  • 11
    Composable
  • 10
    Very easy for beginners
  • 10
    SSR
  • 9
    No runtime overhead
  • 8
    Ease of use
  • 7
    Built in store
  • 4
    Typescript
  • 4
    Templates
  • 4
    Best Developer Experience
  • 3
    Start with pure html + css
  • 1
    Speed
CONS OF SVELTE
  • 1
    Event Listener Overload
  • 1
    Hard to learn
  • 1
    Learning Curve
  • 1
    Complex

related Svelte posts

Sarmad Chaudhary
Founder & CEO at Ebiz Ltd. · | 8 upvotes · 158.2K views

Hi there!

I just want to have a simple poll/vote...

If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:

1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.

2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.

Your advice would help a lot! Thanks in advance :)

See more
React logo

React

89.1K
68.3K
3.7K
A JavaScript library for building user interfaces
89.1K
68.3K
+ 1
3.7K
PROS OF REACT
  • 737
    Components
  • 645
    Virtual dom
  • 552
    Performance
  • 477
    Simplicity
  • 433
    Composable
  • 171
    Data flow
  • 156
    Declarative
  • 121
    Isn't an mvc framework
  • 111
    Reactive updates
  • 109
    Explicit app state
  • 28
    JSX
  • 20
    Learn once, write everywhere
  • 17
    Uni-directional data flow
  • 16
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 9
    Great perfomance
  • 6
    Built by Facebook
  • 4
    Feels like the 90s
  • 4
    Speed
  • 4
    Scalable
  • 3
    Functional
  • 3
    Javascript
  • 3
    Easy to start
  • 3
    Server side views
  • 2
    TypeScript support
  • 2
    Great migration pathway for older systems
  • 2
    SSR
  • 2
    Fast evolving
  • 2
    Simple, easy to reason about and makes you productive
  • 2
    Fancy third party tools
  • 2
    Excellent Documentation
  • 2
    Scales super well
  • 2
    Just the View of MVC
  • 2
    Server Side Rendering
  • 2
    Awesome
  • 2
    Cross-platform
  • 2
    Hooks
  • 2
    Rich ecosystem
  • 1
    Split your UI into components with one true state
  • 1
    Props
  • 1
    Fragments
  • 1
    Sharable
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Super easy
  • 1
    Beautiful and Neat Component Management
  • 1
    Has functional components
  • 1
    Very gentle learning curve
  • 1
    Closer to standard JavaScript and HTML than others
  • 1
    Sdfsdfsdf
  • 1
    Strong Community
  • 1
    Has arrow functions
  • 1
    Allows creating single page applications
  • 1
    Simple
  • 0
    Start simple
CONS OF REACT
  • 31
    Requires discipline to keep architecture organized
  • 19
    No predefined way to structure your app
  • 18
    Need to be familiar with lots of third party packages
  • 6
    JSX
  • 6
    Not enterprise friendly
  • 1
    State consistency with backend neglected
  • 1
    One-way binding only

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.3M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Johnny Bell
Software Engineer at Weedmaps · | 26 upvotes · 284.5K views
Shared insights
on
Vue.jsVue.jsReactReact

I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

See more
Polymer logo

Polymer

386
417
154
A new library built on top of Web Components, designed to leverage the evolving web platform on modern...
386
417
+ 1
154
PROS OF POLYMER
  • 52
    Web components
  • 30
    Material design
  • 21
    Backed by Google
  • 14
    HTML
  • 13
    Components
  • 11
    Data Binding
  • 5
    Open source
  • 4
    It uses the platform
  • 3
    Designer friendly. HTMLX concepts
  • 1
    Like the interesting naming convention for elements
CONS OF POLYMER
  • 1
    Last version is like 2 years ago? that's totally rad

related Polymer posts

Adam Rabinovitch
Global Technical Recruiting Lead & Engineering Evangelist at Beamery · | 5 upvotes · 108.7K views

At Beamery we had a large, AngularJS app, built over several years. Our clients were happy, but we were not. We had several problems: Building new features was slow. AngularJS doesn’t scale nicely. Features clash with each other. Isolation doesn’t come as standard, you have to work hard to keep features separate. It takes time to get it right. #Hiring was hard, for all the reasons listed above. The app was slower than it needed to be because AngularJS was never built for speed. We wanted to render half a million contacts, and Angular was fighting us all the way.

As time went by it become harder to find developers who would willingly choose AngularJS over React Angular 2 , Vue.js , Aurelia or Polymer .

So we faced a choice. We could throw it all away and start again, we could upgrade to Angular 5, or the awesome option - we could use micro frontends. We chose the awesome option.

See more
Ido Shamun
at The Elegant Monkeys · | 5 upvotes · 81.4K views
Shared insights
on
Vue.jsVue.jsReactReactPolymerPolymer
at

For developing our #frontend applications, we decided to use Vue.js . Being such an easy to learn library, compared to React for example, it made everything so easy. At first we started with Polymer but the existing tooling and small community at the time made us look for alternatives.

See more
React Router logo

React Router

1.4K
920
16
A complete routing solution for React.js
1.4K
920
+ 1
16
PROS OF REACT ROUTER
  • 12
    Because there's not alternative
  • 2
    Extremely easy to use
  • 2
    Similar implementations for React and React Native
CONS OF REACT ROUTER
    Be the first to leave a con

    related React Router posts

    ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

    ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

    React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

    styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

    React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

    Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

    See more

    I'm creating a website with React in my free time, and this is my first time doing this. So far, I've worked with React and React Router, but migrating to Next.js or Gatsby would cover Routing and SEO, which I currently cannot work with. Most things I read say that Next.js is the best solution, but I am trying to decide whether it is worth the time and effort to recreate the site for SEO and speed purposes. Does anyone have suggestions?

    See more
    styled-components logo

    styled-components

    737
    392
    7
    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps...
    737
    392
    + 1
    7
    PROS OF STYLED-COMPONENTS
    • 7
      Very easy to use and integrate
    CONS OF STYLED-COMPONENTS
      Be the first to leave a con

      related styled-components posts

      Johnny Bell
      Software Engineer at Weedmaps · | 14 upvotes · 452.8K views

      For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend.

      Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need.

      We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.

      Also we used React-Mentions for tagging tools and topics in the decisions. Typing @ will let you tag a tool, and typing # will allow you to tag a topic.

      The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li.

      If there are anymore tags you'd love to see added in the composer leave me a comment below and we will look into adding them.

      #StackDecisionsLaunch

      See more

      ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

      ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

      React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

      styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

      React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

      Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

      See more
      Angular CLI logo

      Angular CLI

      696
      541
      0
      A command line interface for Angular
      696
      541
      + 1
      0
      PROS OF ANGULAR CLI
        Be the first to leave a pro
        CONS OF ANGULAR CLI
          Be the first to leave a con

          related Angular CLI posts

          Vaibhav Taunk
          Team Lead at Technovert · | 31 upvotes · 1.3M views

          I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

          See more

          Picked Angular 2 as framework since Angular CLI made it easy to get started on a self-contained frontend web project with TypeScript for easier development -- thanks to intellisense extensions for Visual Studio Code, hassle-free browser compatibility with the built-in Babel transpiler and packaging with the built-in Webpack configuration.

          See more
          Ant Design logo

          Ant Design

          642
          1K
          155
          A set of high-quality React components
          642
          1K
          + 1
          155
          PROS OF ANT DESIGN
          • 30
            Lots of components
          • 24
            Polished and enterprisey look and feel
          • 15
            Easy to integrate
          • 14
            Es6 support
          • 14
            TypeScript
          • 13
            Beautiful and solid
          • 12
            Quick Release rhythm
          • 9
            Beautifully Animated Components
          • 9
            Great documentation
          • 9
            Typescript support
          • 6
            Short Code
          CONS OF ANT DESIGN
          • 12
            Less
          • 6
            Large File Size
          • 4
            Close
          • 1
            Poor accessibility support

          related Ant Design posts

          Sarmad Chaudhary
          Founder & CEO at Ebiz Ltd. · | 8 upvotes · 158.2K views

          Hi there!

          I just want to have a simple poll/vote...

          If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:

          1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.

          2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.

          Your advice would help a lot! Thanks in advance :)

          See more
          Shared insights
          on
          Material-UIMaterial-UIAnt DesignAnt Design

          Hi, I start building an admin dashboard with next.js and looking for a frontend framework ( components ready ). So I end up with Ant Design and Material-UI, but I never built a project with these two.

          Here is a list of my requirements.

          1. Good documentation.
          2. easy CRUD ( date picker and date range picker bundled )
          3. built-in multi-lang feature or Great 3rd library support
          4. Admin dashboard template
          5. well code maintenance

          Which is better for the long run?

          See more
          Angular Material  logo

          Angular Material

          469
          542
          25
          Easy to use material design for angular
          469
          542
          + 1
          25
          PROS OF ANGULAR MATERIAL
          • 10
            Components
          • 5
            Backed by a well known company
          • 3
            Simple
          • 2
            Easy
          • 2
            Very good documentation
          • 2
            Rte
          • 1
            Implements well known material design
          CONS OF ANGULAR MATERIAL
          • 2
            Fairly large

          related Angular Material posts