Efficy Overflow Q&A - Recent questions tagged require

Using custom action from User selection page

Mon, 09 Dec 2019 15:58:05 +0000

Dear all,

For a customer we are using the dialog/Users.htm page with a custom action. When the page loads require is undefined when loading the require.config.js file with the overridden action.js. Require is in the Dialog scripts.

Does anyone know of a way to get the overridden action.js?

Best regards,

Rob

Override one function instead of whole module

Wed, 15 Apr 2015 15:26:06 +0000

Is it possible to override one function in the module editView.js without overriding the whole module?

Shim config when library has a dependancy of a custom module

Mon, 01 Dec 2014 16:09:06 +0000

We use some non standard jquery plugins.
I started out by wrapping the library in a define function and put jquery as a dependancy.
But I did it like any other module and did not put it in the shim property because I slightly modified the standard library to use our custom translator module.

So my question is: is there a better alternative if a jquery plugin depends on a custom module other dan wrapping it in a define function like standard modules?

Casing of variables in require.js define functions

Sat, 15 Nov 2014 16:20:55 +0000

Is there a particular reason why format is not starting with a capital, like the other variables for the libs?
Could someone explain (again) when should use PascalCasing or camelBackCasing?

define([

'jquery',

'paperboy',

'base/constants',

'base/model',

'classes/commandListener',

'base/browser',

'utils/format',

'utils/url'

], function($, Paperboy, Const, Model, CommandListener, Browser, format, Url) {

Require.js load new module on every page

Thu, 09 Oct 2014 10:10:11 +0000

I need to load a new module on every page.

What is the best way to accomplish this?

I can make sure that I add it as a dependancy to edit.js, consult.js, .. but is that the best way?

Optimization tool for require.js

Mon, 22 Sep 2014 10:13:53 +0000

Seperating everything into modules is ofcourse the way to go, but the more modules you have, the more http requests are fired.
Assume a project goes live, should we think about using the optimizer for require.js to reduce the number of http requests and js payload when taking into account the possible performance gain?