How to test cross-domain assemblies locally?

Using the dojo toolkit, what is the correct way to locally test code that will run as cross-domain without creating the actual assembly?

It seems that there are three possible options (each with its own shortcomings):

  • Using local (non xd) XMLHttpRequest dojo.require
    • This parameter does not really check the behavior of xd, since it doesjo.require [s] js synchronously via XHR.
  • djConfig.debugAtAllCosts = true;
    • Although this option loads the required code asynchronously (via the script 'tag), it also inserts the code through XHR, parses dojo.require [s] inside it and pulls them. This (using loader_debug), again, is not what loader_xd does. Additional information on this topic in another question.
  • Creating a cross-domain assembly
    • This approach requires assembly, which is not possible in the environment in which I run the code (we use our own build process on the fly, which includes only js that are necessary for a particular one. This process is not suitable for development).

So my question is: is there a way to use loader_xd that does not require xd assembly (which adds xd prefix / suffix for each file)?

( debugAtAllCosts) dojo.require [s]. loader_xd (, , ) , , /, ?

+3
2

, XD- . .

debugAtAllCosts , , , , eval. Firefox , eval- (bootstrap.js) eval, eval, eval- . Firebug , , Dojo XHR eval, . Webkit/Safari . , debugAtAllCosts XD.

+1

peller . .xd.js , /buildscripts/jslib/buildUtilXd.js buildUtilXd.xdgen().

script , /buildscripts/build.js .

, Dojo ( Dojo 2.x ) , script , , - . xd .

+3

Source: https://habr.com/ru/post/1725961/


All Articles