All modules are published in the @extendscript
scope.
Creating a module comprises of four stages:
The first step is to add your module to the API Registry
There are multipple ways to write and validate your code. See our Testing Guide for testing guidelines. It is recommended to use our Boilerplate Module.
A couple of things to double check:
- Name of the package reflects the structure of API Registry and follows the Package Naming Conventions
- Version of the package is correct. We use semantic versioning where initial release for public use is
1.0.0
- The name of the main entry script is the same as last section of module name. Therefore the main script file for
ind.tools.documentbuilder
is calleddocumentbuilder.js
Some things to look out for if you did not use our Boilerplate Module:
- The
package.json
contains aprepublishOnly
script set tonpm config set scope extendscript
- The package contains a
.npmignore
file that exclude all files that should be excluded from the package
Publish your module with the --access public
flag:
npm publish --access public