For me, when I do Immediately invoked function, I need to put ; at the end of require(). Error: const fs = require(‘fs’) (() => { console.log(‘wow’) })() Good: const fs = require(‘fs’); (() => { console.log(‘wow’) })()
Auto-loading works fine as long as the class in your file is a class that is only defined in that file. It doesn’t work if you’re wanting to re-open an existing class (originally defined in standard Ruby, Rails, or another library) and customize it in some way. Example of problem: Here’s an example of a … Read more
You can use the define plugin. I use it by doing something as simple as this in your webpack build file where env is the path to a file that exports an object of settings: // Webpack build config plugins: [ new webpack.DefinePlugin({ ENV: require(path.join(__dirname, ‘./path-to-env-files/’, env)) }) ] // Settings file located at `path-to-env-files/dev.js` … Read more
if (require.main === module) { console.log(‘called directly’); } else { console.log(‘required as a module’); } See documentation for this here: https://nodejs.org/docs/latest/api/modules.html#modules_accessing_the_main_module
The require() idiom is part of a specification known as CommonJS. Specifically, that part of the spec is called ‘Modules’. RequireJS is just one implementation of CommonJS (and it’s usually a browser-side implementation – in fact, it takes a different approach because of the asynchronous nature of the browser). If you look at the list … Read more
Here is the answer: Module.prototype.load = function(filename) { debug(‘load ‘ + JSON.stringify(filename) + ‘ for module ‘ + JSON.stringify(this.id)); assert(!this.loaded); this.filename = filename; this.paths = Module._nodeModulePaths(path.dirname(filename)); var extension = path.extname(filename) || ‘.js’; if (!Module._extensions[extension]) extension = ‘.js’; Module._extensions[extension](this, filename); this.loaded = true; }; Node.JS looks to see if the given module is a core module. … Read more
According to the Meteor documentation, files are currently loaded in this order: Files in [project_root]/lib are loaded first Files are sorted by directory depth. Deeper files are loaded first. Files are sorted in alphabetical order. main.* files are loaded last. Source: http://docs.meteor.com/#structuringyourapp
If you want to inline file contents from fs.readFileSync() calls, you can use brfs: var fs = require(‘fs’); var src = fs.readFileSync(__dirname + ‘/file.txt’); then do: browserify -t brfs main.js > bundle.js and src will be set to the contents of file.txt at compile time.
You can use this to delete its entry in the cache: delete require.cache[require.resolve(‘./b.js’)] require.resolve() will figure out the full path of ./b.js, which is used as a cache key.
You cannot use a variable as argument to require. Webpack needs to know what files to bundle at compile time. As it does no program flow analysis, it can’t know what you pass to the function. In that case it might be obvious, but this could go as far as using user input to decide … Read more