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
I just tried and it works with require “./tokenizer”.
The best explanation I could get is from Tamas Piro’s post. TLDR; TypeScript uses the DOM typings for the global execution environment. In your case there is a ‘co’ property on the global window object. To solve this: Rename the variable, or Use TypeScript modules, and add an empty export{}: export {}; or Configure your … Read more
With define you register a module in require.js that you can then depend on in other module definitions or require statements. With require you “just” load/use a module or javascript file that can be loaded by require.js. For examples have a look at the documentation My rule of thumb: Define: If you want to declare … Read more
The error pretty much explains what the problem is: you are trying to include a file that is not there. Try to use the full path to the file, using realpath(), and use dirname(__FILE__) to get your current directory: require_once(realpath(dirname(__FILE__) . ‘/../includes/dbconn.inc’));
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
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
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 (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