RequireJS Reviews & Product Details

1) Manage Dependencies in Modular programming (Asynchoronous) and its open source under MIT license.

2) It has set of following plugins like text, domReady, i18n, CSS loading.

3) OJET (Oracle javascript Extension Toolit) which is a popular javascript framework from oracle used requirejs and knockout to build its library that we can use for corporate products.

4) Optimizer in requirejs Combines script files together with the help of UglifyJS and combine CSS files together. Review collected by and hosted on G2.com.

I dont find any disadvantages as it is very flexibale and can be used in modular programming to increase speed and code quality Review collected by and hosted on G2.com.

It offers a powerful and efficient way of managing dependencies between javascript files in a web project. Instead of adding multiple script tags in a html file, all the you need is add one script tag to import the require library which takes care of importing the desired javascript files and their dependencies Review collected by and hosted on G2.com.

There are probably no disadvantages to using require.js because it simplifies your project structure and performance Review collected by and hosted on G2.com.

RequireJS brings the convenience of lazy file loading, thereby, also reducing the startup time and consuming less browser cache. With RequireJS, the developer doesn't need to take care of the order in which all the different Javascript files need to be defined, as it can be handled with the data-main attribute mentioned with initializing RequireJS file in the HTML page. Review collected by and hosted on G2.com.

Though RequireJS provides good code splitting support, it is sometimes a pain to set up RequireJS with Node Package Manager (NPM). Also, if your code splitting strategy is not right, RequireJS would throw errors which are very difficult to backtrack. Review collected by and hosted on G2.com.

RequireJS is a JavaScript file and module loader. It is optimized for in-browser use, but it can be used in other JavaScript environments, like NodeJS. Using a modular script loader like RequireJS will improve the speed and quality of your code. Makes life easier for you, for your developers, for the people reading your code. And reduces complication thus reduces chances of error. Review collected by and hosted on G2.com.

Honestly, not much. It's requirejs. It does its job and it does it's job well. What is there to complain about? And it's community on github is super helpful and responsive. There really isn't anything to dislike about it. Review collected by and hosted on G2.com.

RequrieJS uses Asynchronous Module Loading (AMD) technique for the loading of files. In the technique of AMD, each dependent module loads in the given order through an asynchronous way.

-easy to refactor whole front-end by using aliases for modules in your config file

-tight and clear control of dependencies and loading order

-define statements are a gentle reminder that you are working on frontend not backend JS

-does not require a build step, unlike Browserify or Webpack, the feature which truly facilitates hot-reloading Review collected by and hosted on G2.com.

-Third-party libs need to be AMD compatible which can be complicated with some scripts

-Extra code for function wrappers and loader shim

-AMD is not a real standard, just some sort of proposition that gained some traction in the JS community Review collected by and hosted on G2.com.

Easy to use libraries.

Compatible with most of the modern browsers.

Also supported with JQuery.

Pre-defined folder structure. Review collected by and hosted on G2.com.

Not much online help available on using the library available.

Error handling and exception management is difficult in Require JS.

anonymous define error is too common. Review collected by and hosted on G2.com.

1) Simple

2) Easy to refactor whole front-end by using aliases for modules in your config file

3) Tight and clear control of dependencies and loading order

4) Define statements are a gentle reminder that you are working on frontend not backend JS

5) Optimizer can create one deployment file for a single entry point SPA or multiple deployment files for a multiple entry point SPA Review collected by and hosted on G2.com.

1.It needs multiple HTTP requests to load those files, which will slow down the performance of the page

2.You need to manually keep them in the correct order - e.g. the first file is jQuery and the ones after it might be jQuery plugins that obviously need jQuery to be loaded first Review collected by and hosted on G2.com.

With Requirejs it is easy to refactor whole front-end by using aliases for modules in your config file.

It has a tight and clear control of dependencies and loading order

,defines statements show you are working on frontend not backend JS.

r.js optimizer can create one deployment file for a single entry point SPA or multiple deployment files

It does not require a build step, unlike browserify or Webpack

The feature which truly facilitates hot-reloading Review collected by and hosted on G2.com.

Nothing really. It does what you need it to do pretty efficiently I can't think of anything negative about that. Review collected by and hosted on G2.com.

Javascript isn't the easiest language to use and RequireJS is best at letting me import modules into marketing analyst workflows easily. Review collected by and hosted on G2.com.

RequireJS requires you to have some type of programming background. Review collected by and hosted on G2.com.

RequireJs is simple and easy to work with in whole front end by using modules and configuration files,We can control dependency and order of loading.defining statements in Requirejs is a gentle reminder for frontend. r.js creates one deployment file, Review collected by and hosted on G2.com.

1.The Require optimizer is the worst.

2.It is not modular.

3.some times unable to respond. Review collected by and hosted on G2.com.