You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
The main reason is that the nodejs module.children and require objects use the full path of the module entry point as properties. It is more convenient to see and use this as the module name too.
I believe it will encourage proper usage practice in newcomers as well.
In the ```npm init`` command below the (index.js) should be (example_module) instead.
package name: (example_module)
version: (1.0.0)
description:
entry point: (index.js) <-- this should be (example_module)
test command:
git repository:
keywords:
author:
license: (ISC)
About to write to /home/nickali/Restarian/example_module/package.json:
{
"name": "example_module",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "",
"license": "ISC"
}
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The main reason is that the nodejs module.children and require objects use the full path of the module entry point as properties. It is more convenient to see and use this as the module name too.
I believe it will encourage proper usage practice in newcomers as well.
In the ```npm init`` command below the (index.js) should be (example_module) instead.
The text was updated successfully, but these errors were encountered: