Alternatives to Angular CLI logo

Alternatives to Angular CLI

AngularJS, Webpack, Angular 2, npm, and React are the most popular alternatives and competitors to Angular CLI.
737
586
+ 1
0

What is Angular CLI and what are its top alternatives?

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 CLI is a tool in the JavaScript Framework Components category of a tech stack.
Angular CLI is an open source tool with 24.6K GitHub stars and 11.1K GitHub forks. Here鈥檚 a link to Angular CLI's open source repository on GitHub

Top Alternatives to Angular CLI

  • AngularJS

    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML鈥檚 syntax to express your application鈥檚 components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • Webpack

    Webpack

    A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff. ...

  • Angular 2

    Angular 2

    It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications. ...

  • npm

    npm

    npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day. ...

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

  • gulp

    gulp

    Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes. ...

  • 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 alternatives & related posts

AngularJS logo

AngularJS

41.9K
29.7K
5.3K
Superheroic JavaScript MVW Framework
41.9K
29.7K
+ 1
5.3K
PROS OF ANGULARJS
  • 886
    Quick to develop
  • 587
    Great mvc
  • 571
    Powerful
  • 522
    Restful
  • 504
    Backed by google
  • 349
    Two-way data binding
  • 344
    Javascript
  • 328
    Open source
  • 306
    Dependency injection
  • 198
    Readable
  • 76
    Fast
  • 65
    Directives
  • 64
    Great community
  • 57
    Free
  • 39
    Extend html vocabulary
  • 30
    Components
  • 26
    Easy to test
  • 25
    Easy to learn
  • 24
    Easy to templates
  • 24
    Great documentation
  • 22
    Easy to start
  • 18
    Awesome
  • 18
    Light weight
  • 15
    Angular 2.0
  • 15
    Javascript mvw framework
  • 14
    Great extensions
  • 14
    Efficient
  • 11
    Easy to prototype with
  • 9
    High performance
  • 9
    Coffeescript
  • 8
    Mvc
  • 8
    Two-way binding
  • 8
    Lots of community modules
  • 7
    Easy to e2e
  • 7
    Clean and keeps code readable
  • 6
    One of the best frameworks
  • 6
    Easy for small applications
  • 5
    Works great with jquery
  • 5
    Fast development
  • 3
    Hierarchical Data Structure
  • 3
    The two-way Data Binding is awesome
  • 3
    Community
  • 3
    Typescript
  • 3
    Declarative programming
  • 3
    I do not touch DOM
  • 3
    Be a developer, not a plumber.
  • 3
    Dart
  • 2
    Fkin awesome
  • 2
    Scopes
  • 2
    The powerful of binding, routing and controlling routes
  • 2
    Opinionated in the right areas
  • 2
    Supports api , easy development
  • 2
    Common Place
  • 2
    Amazing community support
  • 2
    Great
  • 2
    Very very useful and fast framework for development
  • 2
    Readable code
  • 2
    Programming fun again
  • 2
    Linear learning curve
  • 1
    Bot Ionescu
  • 1
    Acoperi葯ul 0757604335
  • 1
    Js
  • 1
    Google.com
  • 1
    Angular js
  • 1
    Http葯//Acoperi葯ul 0757604335
  • 1
    Shvzjn
CONS OF ANGULARJS
  • 10
    Complex
  • 3
    Dependency injection
  • 2
    Learning Curve
  • 2
    Event Listener Overload
  • 1
    Hard to learn

related AngularJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH | 24 upvotes 路 1.7M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API鈥檚 resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH | 19 upvotes 路 575.2K 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
Webpack logo

Webpack

25.9K
17.8K
750
A bundler for javascript and friends
25.9K
17.8K
+ 1
750
PROS OF WEBPACK
  • 308
    Most powerful bundler
  • 182
    Built-in dev server with livereload
  • 143
    Can handle all types of assets
  • 87
    Easy configuration
  • 20
    Laravel-mix
  • 4
    Overengineered, Underdeveloped
  • 2
    Makes it easy to bundle static assets
  • 2
    Webpack-Encore
  • 1
    Better support in Browser Dev-Tools
  • 1
    Redundant
CONS OF WEBPACK
  • 11
    Hard to configure
  • 2
    Spaghetti-Code out of the box
  • 2
    SystemJS integration is quite lackluster
  • 2
    Loader architecture is quite a mess (unreliable/buggy)
  • 2
    Fire and Forget mentality of Core-Developers
  • 2
    No clear direction

related Webpack posts

Jonathan Pugh
Software Engineer / Project Manager / Technical Architect | 25 upvotes 路 1.4M views

I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

So that's my latest mobile stack. What tools do you use? Have you tried these ones?

See more
Johnny Bell
Software Engineer at Weedmaps | 19 upvotes 路 1.2M views

So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

See more
Angular 2 logo

Angular 2

4.4K
3.4K
410
A platform for building mobile and desktop web applications
4.4K
3.4K
+ 1
410
PROS OF ANGULAR 2
  • 93
    It's a powerful framework
  • 47
    Straight-forward architecture
  • 39
    Great UI and Business Logic separation
  • 38
    TypeScript
  • 37
    Powerful, maintainable, fast
  • 33
    Amazing CLI
  • 30
    Great mvc
  • 22
    Powerfull Dependency Injection
  • 17
    Easy to build
  • 13
    Opinionated, batteries-included approach
  • 9
    All in one Framework
  • 7
    Solid Standard Setup.
  • 7
    Schematics
  • 6
    Structured
  • 5
    Performance
  • 3
    Only for single page applications
  • 3
    Complex
  • 1
    Builders
  • 0
    React
CONS OF ANGULAR 2
  • 8
    Large overhead in file size and initialization time
  • 8
    Overcomplicated
  • 2
    Ugly code
  • 2
    Cringe
  • 2
    CLI not open to other test and linting tools

related Angular 2 posts

When Redash was created 5 years ago we chose AngularJS as our frontend framework, but as AngularJS was replaced by Angular 2 we had to make a new choice. We decided that we won't migrate to Angular, but to either React or Vue.js. Eventually we decided to migrate to React for the following reasons:

  1. Many in our community are already using React internally and will be able to contribute.
  2. Using react2angular we can do the migration gradually over time instead of having to invest in a big rewrite while halting feature development.

So far the gradual strategy pays off and in the last 3 major releases we already shipped React code in the Angular.js application.

See more
Max Musing
Founder & CEO at BaseDash | 10 upvotes 路 182.3K views

From my experience of the early startup world, a majority of companies these days use Node.js. Python and Go are the next biggest languages, but significantly smaller than Node.

However, if you're having trouble with the front end aspect of Django, using Node probably won't make that easier for you. You'll have a lot more options between front end frameworks (React, Vue.js, Angular 2) , but they'll definitely take more time to learn than Django's templating system.

Think about whether you want to focus on front end or back end for now, and make a decision from there.

See more
npm logo

npm

61K
46.3K
1.6K
The package manager for JavaScript.
61K
46.3K
+ 1
1.6K
PROS OF NPM
  • 649
    Best package management system for javascript
  • 382
    Open-source
  • 327
    Great community
  • 147
    More packages than rubygems, pypi, or packagist
  • 112
    Nice people matter
  • 5
    Audit feature
  • 4
    Good following
  • 4
    As fast as yarn but really free of facebook
  • 1
    Stability
  • 1
    Super fast
CONS OF NPM
  • 5
    Problems with lockfiles
  • 5
    Bad at package versioning and being deterministic
  • 3
    Node-gyp takes forever
  • 1
    Super slow

related npm posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH | 24 upvotes 路 1.7M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API鈥檚 resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Johnny Bell
Software Engineer at Weedmaps | 19 upvotes 路 1.2M views

So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

See more
React logo

React

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

related React posts

Vaibhav Taunk
Team Lead at Technovert | 31 upvotes 路 1.5M 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 路 382.3K views
Shared insights
on
Vue.js
React

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
gulp logo

gulp

9.9K
7K
1.7K
The streaming build system
9.9K
7K
+ 1
1.7K
PROS OF GULP
  • 454
    Build speed
  • 277
    Readable
  • 244
    Code-over-configuration
  • 210
    Open source
  • 175
    Node streams
  • 107
    Intuitive
  • 84
    Lots of plugins
  • 66
    Works great with browserify
  • 45
    Easy to Learn
  • 17
    Laravel-elixir
  • 4
    build workflow
  • 3
    Great community
  • 3
    Simple & flexible
  • 2
    Stylus intergration
  • 2
    jade intergration
  • 0
    Well documented
  • 0
    Clean Code
CONS OF GULP
    Be the first to leave a con

    related gulp posts

    I use JavaScript these days and for few years I didn't have to use jQuery at all. I used to use it back in the days when IE8 and similar was a thing. But due to better browser support of native functions for DOM manipulation I could move to vanilla JavaScript. Most of the time, that's all I need to work with modals/accordions and similar. But I'm not saying that jQuery is bad. It was, and still is a great tool. Some of it's features are available in all browsers nowadays so it is not so important as it used to be. But jQuery has still advantage for example in it's selector engine, some DOM selections which are easy in jQuery are a bit more difficult in vanilla JS (you have to create some helper functions or use some 3rd party library to help you with that), but to be honest I needed this on very few occasions. So it really depends on your project (supported browses, plain JS or some bundling - gulp, Webpack, whether you plan to use modules etc.). Hope this helps.

    See more
    Gustavo Mu帽oz
    Web UI Developer at Globant | 4 upvotes 路 627.1K views
    Shared insights
    on
    Webpack
    Grunt
    gulp
    Parcel

    Using Webpack is one of the best decision ever. I have used to Grunt and gulp previously, but the experience is not the same, and despite I know there are other bundlers like Parcel, Webpack gives me the perfect balance between automatization and configuration. The ecosystem of tools and loaders is amazing, and with WebPack #merge, you can modularize your build and define standard pieces to assemble different build configurations. I don't like processes where you cannot see their guts, and you have to trust in magic a little bit too much for my taste. But also I don't want to reinvent the wheel and lose too much time configuring my build processes. And of course, I love #WebPackDevServer and hot reloading.

    See more
    React Router logo

    React Router

    1.4K
    941
    12
    A complete routing solution for React.js
    1.4K
    941
    + 1
    12
    PROS OF REACT ROUTER
    • 12
      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
      styled-components logo

      styled-components

      798
      423
      7
      Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps...
      798
      423
      + 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 路 470.9K 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