Alternatives to Glamorous logo

Alternatives to Glamorous

styled-components, React Router, Storybook, Ant Design, and Angular CLI are the most popular alternatives and competitors to Glamorous.
15
34
+ 1
0

What is Glamorous and what are its top alternatives?

Glamorous is React component styling solved with an elegant (inspired) API, small footprint (<5kb gzipped), and great performance (via glamor). It has a very similar API to styled-components and uses similar tools under the hood (glamor).
Glamorous is a tool in the JavaScript Framework Components category of a tech stack.
Glamorous is an open source tool with 3.7K GitHub stars and 267 GitHub forks. Here鈥檚 a link to Glamorous's open source repository on GitHub

Top Alternatives to Glamorous

  • styled-components
    styled-components

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

  • 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. ...

  • Storybook
    Storybook

    It is an open source tool for developing UI components in isolation for React, Vue, and Angular. It makes building stunning UIs organized and efficient. ...

  • 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 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. ...

  • 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. ...

  • Vue CLI
    Vue CLI

    Vue CLI aims to be the standard tooling baseline for the Vue ecosystem. It ensures the various build tools work smoothly together with sensible defaults so you can focus on writing your app instead of spending days wrangling with config. ...

  • Angular Universal
    Angular Universal

    It executes on the server, generating static application pages that later get bootstrapped on the client. This means that the application generally renders more quickly, giving users a chance to view the application layout before it becomes fully interactive. ...

Glamorous alternatives & related posts

styled-components logo

styled-components

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

    related styled-components posts

    Johnny Bell

    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
    React Router logo

    React Router

    2.7K
    1.1K
    13
    A complete routing solution for React.js
    2.7K
    1.1K
    + 1
    13
    PROS OF REACT ROUTER
    • 13
      Because there's not alternative
    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
      Storybook logo

      Storybook

      1.2K
      542
      0
      Build bulletproof UI components faster
      1.2K
      542
      + 1
      0
      PROS OF STORYBOOK
        Be the first to leave a pro
        CONS OF STORYBOOK
          Be the first to leave a con

          related Storybook posts

          Robert Zuber

          We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

          See more
          Shared insights
          on
          BitBitStorybookStorybook

          Hi Team,

          I need a UI component library where i should be able to integrate with the Angular framework and develop components and again i should be able to deploy them in an isolated environment which should not impact the app.

          I am using Storybook, due to some glitch in storybook new version, We could not able to see the source code in the deployed version.

          We mainly use storybook for demo purposes where we show the code as well. So please help, can I use Bit for my requirement?

          See more
          Ant Design logo

          Ant Design

          970
          1.6K
          219
          A set of high-quality React components
          970
          1.6K
          + 1
          219
          PROS OF ANT DESIGN
          • 47
            Lots of components
          • 33
            Polished and enterprisey look and feel
          • 21
            TypeScript
          • 20
            Easy to integrate
          • 18
            Es6 support
          • 17
            Beautiful and solid
          • 17
            Typescript support
          • 16
            Beautifully Animated Components
          • 15
            Quick Release rhythm
          • 14
            Great documentation
          • 2
            Easy to customize Forms
          CONS OF ANT DESIGN
          • 21
            Less
          • 10
            Large File Size
          • 4
            Poor accessibility support
          • 1
            Dangerous to use as a base in component libraries

          related Ant Design posts

          Sarmad Chaudhary
          Founder & CEO at Ebiz Ltd. | 9 upvotes 路 640.7K 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

          Hello, A question to frontend developers. I am a beginner on frontend.

          I am building a UI for my company to replace old legacy one with React and this question is about choosing how to apply design to it.

          I have Tailwind CSS on one hand and Ant Design on the other (I didnt like mui and Bootstrap doesn't seem to have enterprise components as ant) As far as I understand, tailwind is great. It allows me to literally build an application without touching the css but I have to build my own react components with it. Ant design or mantine has ready to use components which I can use and rapidly build my application.

          My question is, is it the right approach to: - Use a component framework for now and replace legacy app. - Introduce tailwind later when I have a frontend resource in hand and then build own component library

          Thank you.

          See more
          Angular CLI logo

          Angular CLI

          886
          726
          0
          A command line interface for Angular
          886
          726
          + 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 路 2.2M 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
              Angular Material  logo

              Angular Material

              606
              705
              32
              Easy to use material design for angular
              606
              705
              + 1
              32
              PROS OF ANGULAR MATERIAL
              • 12
                Components
              • 8
                Backed by a well known company
              • 4
                Simple
              • 3
                Easy
              • 2
                Very good documentation
              • 2
                Rte
              • 1
                Implements well known material design
              CONS OF ANGULAR MATERIAL
              • 4
                Fairly large

              related Angular Material posts

              Vue CLI logo

              Vue CLI

              431
              450
              3
              Standard Tooling for Vue.js Development
              431
              450
              + 1
              3
              PROS OF VUE CLI
              • 1
                GUI for installing dependencies
              • 1
                Visual Web Interface
              • 1
                Detects and run npm tasks
              CONS OF VUE CLI
                Be the first to leave a con

                related Vue CLI posts

                Simon Reymann
                Senior Fullstack Developer at QUANTUSflow Software GmbH | 22 upvotes 路 1.6M views

                Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

                • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
                • Vue Styleguidist as our style guide and pool of developed Vue.js components
                • Vuetify as Material Component Framework (for fast app development)
                • TypeScript as programming language
                • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
                • ESLint, TSLint and Prettier for coding style and code analyzes
                • Jest as testing framework
                • Google Fonts and Font Awesome for typography and icon toolkit
                • NativeScript-Vue for mobile development

                The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

                • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
                • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
                • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
                • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
                • Large scaling. Vue.js can help to develop pretty large reusable templates.
                • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
                See more

                I am trying to build a Cordova app using Vue.js and Quasar Framework, should I use the Vue CLI or quasar CLI? Which would be better for extensibility?

                See more
                Angular Universal logo

                Angular Universal

                329
                396
                36
                A technology that renders Angular applications on the server
                329
                396
                + 1
                36
                PROS OF ANGULAR UNIVERSAL
                • 7
                  Typescript
                • 5
                  Complete Framework
                • 5
                  Server rendering and code splitting
                • 4
                  Static site generator
                • 4
                  Dynamic rendering
                • 4
                  Same existing code base for both SPA and SSR
                • 3
                  Easy setup
                • 3
                  SEO
                • 1
                  Well documented
                CONS OF ANGULAR UNIVERSAL
                  Be the first to leave a con

                  related Angular Universal posts