If not you can run meteor npm init to create one. If you create a new Meteor project, you will have such a file created for you. Npm packages are configured in a package.json file at the root of your project. In other words, leave meteor-node-stubs installed unless you really know what you’re doing. Meteor’s module system avoids actually bundling any stub modules (and their dependencies) if they are not used, so there is no cost to keeping meteor-node-stubs in the dependencies. The meteor-node-stubs npm package provides browser-friendly implementations of Node’s built-in modules, like path, buffer, util, etc.
If you are upgrading an application to Meteor 1.3 you may have to run meteor npm install -save meteor-node-stubs manually. When creating a new application Meteor installs the meteor-node-stubs npm package to help provide this client browser compatibility. In most cases, you can import npm dependencies from a client file, just as you would on the server.
Tools like browserify and webpack are designed to provide a Node-like environment on the client so that many npm packages, even ones originally intended for the server, can run unmodified. There are also sites that search certain types of packages, like js.coach‘s React and React Native sections. You can use the official search at or see results sorted by package quality (code quality, maintenance status, development velocity, popularity etc.) at npms.io.
0 kommentar(er)
