FilesExpand file tree

master

/

node.js

Copy path

Blame

More file actions

Blame

More file actions

Latest commit

 

History

History

History

77 lines (65 loc) · 2.96 KB

master

/

node.js

Copy path

Top

File metadata and controls

• Code
• Blame

77 lines (65 loc) · 2.96 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

define(["./_base/kernel", "./has", "require"], function(kernel, has, require){

var nodeRequire = kernel.global.require && kernel.global.require.nodeRequire;

if (!nodeRequire) {

throw new Error("Cannot find the Node.js require");

}

var module = nodeRequire("module");

return {

// summary:

// This AMD plugin module allows native Node.js modules to be loaded by AMD modules using the Dojo

// loader. This plugin will not work with AMD loaders that do not expose the Node.js require function

// at `require.nodeRequire`.

//

// example:

// | require(["dojo/node!fs"], function(fs){

// | var fileData = fs.readFileSync("foo.txt", "utf-8");

// | });

load: function(/*string*/ id, /*Function*/ contextRequire, /*Function*/ load){

/*global define:true */

// The `nodeRequire` function comes from the Node.js module of the AMD loader, so module ID resolution is

// relative to the loader's path, not the calling AMD module's path. This means that loading Node.js

// modules that exist in a higher level or sibling path to the loader will cause those modules to fail to

// resolve.

//

// Node.js does not expose a public API for performing module filename resolution relative to an arbitrary

// directory root, so we are forced to dig into the internal functions of the Node.js `module` module to

// use Node.js's own path resolution code instead of having to duplicate its rules ourselves.

//

// Sooner or later, probably around the time that Node.js internal code is reworked to use ES6, these

// methods will no longer be exposed and we will have to find another workaround if they have not exposed

// an API for doing this by then.

if(module._findPath && module._nodeModulePaths){

var localModulePath = module._findPath(id, module._nodeModulePaths(contextRequire.toUrl(".")));

if (localModulePath !== false) {

id = localModulePath;

}

}

var oldDefine = define,

result;

// Some modules attempt to detect an AMD loader by looking for global AMD `define`. This causes issues

// when other CommonJS modules attempt to load them via the standard Node.js `require`, so hide it

// during the load

define = undefined;

try {

result = nodeRequire(id);

}

finally {

define = oldDefine;

}

load(result);

},

normalize: function (/**string*/ id, /*Function*/ normalize){

// summary:

// Produces a normalized CommonJS module ID to be used by Node.js `require`. Relative IDs

// are resolved relative to the requesting module's location in the filesystem and will

// return an ID with path separators appropriate for the local filesystem

if (id.charAt(0) === ".") {

// absolute module IDs need to be generated based on the AMD loader's knowledge of the parent module,

// since Node.js will try to use the directory containing `dojo.js` as the relative root if a

// relative module ID is provided

id = require.toUrl(normalize("./" + id));

}

return id;

}

};

});