As we're using GitHub's registry, this will be set to "" publishConfig.access This field tells NPM which registry to publish our package to. If it's not, you'll have to add this information before you'll be able to publish. Depending on how you first set up your package, this is probably filled in. GitHub needs the repository field to know which repo to publish a package to. We'll be building our code ( index.ts) into the dist, so our main will be dist/index.js. This is the file that will be loaded when someone imports/requires our module. The main property tells NPM which file is the entrypoint to our package. My account is jonathan-wilkinson and I'm publishing my nodash package, so my package name will be main ![]() ![]() Scopes are a way to group packages by indvidual or organisation and are named When using GitHub Packages your scope will be the name of the GitHub account that owns the repository you're publishing to.
0 Comments
Leave a Reply. |