Do I just have to include mongoose as a dependency as well in the parent app or is there a way of getting access to that module by way of the child? While it’s possible for you to e.g. require(‘github/node_modules/mongoose’), the standard practice is to install all of your dependencies explicitly (i.e., you should include … Read more
This can be set up on your tsconfig.json file, as it is a TypeScript feature. You can do like this: “compilerOptions”: { “baseUrl”: “src”, // This must be specified if “paths” is. … “paths”: { “@app/*”: [“app/*”], “@config/*”: [“app/_config/*”], “@environment/*”: [“environments/*”], “@shared/*”: [“app/_shared/*”], “@helpers/*”: [“helpers/*”] }, … Have in mind that the path, where you … Read more
Use: npm update -g npm See the documentation for the update command: npm update [-g] [<pkg>…] This command will update all the packages listed to the latest version (specified by the tag config), respecting semver. Additionally, see the documentation on Node.js and NPM installation and Upgrading NPM. The following original answer is from the old … Read more
What is the purpose of node_modules folder? You can think of the node_modules folder like a cache for the external modules that your project depends upon. When you npm install them, they are downloaded from the web and copied into the node_modules folder and Node.js is trained to look for them there when you import … Read more
You want to assign the value of module.exports to be your default function, and then put all the named exports as properties on that function. const defaultFunction = () => { console.log(‘default!’); }; const namedFunction1 = () => { console.log(‘1!’); }; const namedFunction2 = () => { console.log(‘2!’); }; const myModule = module.exports = defaultFunction; … Read more
When you did the command npm init, there were probably some relevant questions you needed to answer. Specifically, the name of your module. When you use npm init, it assumes you want the name of the module you’re creating to be called the name of the folder it is in. So it’s not the name … Read more
I had the same problem; I fixed it by installing the babel-loader module: yarn add -D babel-loader or npm install –save babel-loader
I was able to fix this issue by using yarn instead of npm.
You can export multiple classes like this: e.g. People.js class Jack{ //Member variables, functions, etc } class John{ //Member variables, functions, etc } module.exports = { Jack : Jack, John : John } And access these classes as you have correctly mentioned: var People = require(‘./People.js’); var JackInstance = new People.Jack(); var JohnInstance = new … Read more
The “parent” is the module that caused the script to be interpreted (and cached), if any: // $ node foo.js console.log(module.parent); // `null` // require(‘./foo’) console.log(module.parent); // `{ … }` What you’re expecting is the “caller,” which Node doesn’t retain for you. For that, you’ll need the exported function you’re currently using to be a … Read more