Change a.js to export the variable: exports.test = “Hello World”; and assign the return value of require(‘./a.js’) to a variable: var a = require(‘./a.js’); console.log(a.test); Another pattern you will often see and probably use is to assign something (an object, function) to the module.exports object in a.js, like so: module.exports = { big: “string” };
The path is relative to the directory in which you are requireing the files, so it should be something like: var couch = require(‘./couch’); var config = require(‘../config’); A bit of clarification, if you write var couch = require(‘./couch’); you are trying to require the couch module which resides in the current directory, if you … Read more
function requireFromString(src, filename) { var Module = module.constructor; var m = new Module(); m._compile(src, filename); return m.exports; } console.log(requireFromString(‘module.exports = { test: 1}’, ”)); look at _compile, _extensions and _load in module.js
The equivalent is simply: import “./filename”; Here are some of the possible syntax variations: import defaultMember from “module-name”; import * as name from “module-name”; import { member } from “module-name”; import { member as alias } from “module-name”; import { member1 , member2 } from “module-name”; import { member1 , member2 as alias2 , […] … Read more
Source code is here. exports/require are not keywords, but global variables. Your main script is wrapped before start in a function which has all the globals like require, process etc in its context. Note that while module.js itself is using require(), that’s a different require function, and it is defined in the file called “node.js” … Read more
require (and its cousin load) are core Ruby methods. require_dependency is a method that helps Rails handle the problem of dependency management. Long story short, it allows Rails to reload classes in development mode so that you don’t have to restart the server each time you make a code change. The Rails framework will require_dependency … Read more
For Electron version 12 and above const electron = require(“electron”); const { app, BrowserWindow } = electron; app.on(“ready”, () => { const mainWindow = new BrowserWindow({ width: 1000, height: 600, webPreferences: { nodeIntegration: true, contextIsolation: false, enableRemoteModule: true, }, }); mainWindow.loadURL(`file://${__dirname}/index.html`); });
You can’t mix import and module.exports. In the import world, you need to export things. // Change this module.exports = foo; // To this export default foo;
They are exactly the same. The reason is some environments might already have a require, in which case RequireJS doesn’t overwrite it and allows usage of the library through requirejs See this commit – https://github.com/jrburke/requirejs/commit/be45948433b053921dc6a6a57bf06d04e13b3b39
When you call lib = require(“lib.js”)(params) You’re actually calling lib.js with one parameter containing two properties name app and param2 You either want // somefile require(“lib.js”)(params); // lib.js module.exports = function(options) { var app = options.app; var param2 = options.param2; }; or // somefile require(“lib.js”)(app, param2) // lib.js module.exports = function(app, param2) { }