Modern Full-Stack Development

homepage – If your project has a web site, then you can specify the 
URL of its homepage with this element.
• 
keywords – The keywords element is an arbitrary array of strings that 
can be used to help people find your package (more on this in the 
next section).
• 
license – The value of the license element is the license your 
package is released under. The value of this must be a currently 
registered SPDX license identifier (see 
spdx.org
 for a list). 
Alternatively, if you are using a custom license or one that doesn’t yet 
have an SPDX identifier, then you can set the value to "SEE LICENSE 
IN " and place the  license file alongside the 
package.json file. Or, if you don’t grant rights to use your package to 
anyone (vis-à-vis, you want to make it private and/or unpublished), 
then you can use a value of "UNLICENSED".
Chapter 2   a Few More words: advanCed node and npM

---

24
• 
man – With this element you can specify a single file or an array of 
filenames to put in place for the Linux man program to display for 
your package.
• 
main – This is the primary entry point to your package. For example, 
if your package is named super_duper_cool_package, then a user 
will expect to be able to do require("super_duper_cool_package") 
after they install it. To allow this, the main element must point to the 
file that exports your package’s main export object.
•