@trii/trii-classes-definitions

Introduction

TODO: Give a short introduction of your project. Let this section explain the objectives or the motivation behind this project.

Getting Started

TODO: Guide users through getting your code up and running on their own system. In this section you can talk about:

• Installation process
• Software dependencies
• Latest releases
• API references

Build and Test

TODO: Describe and show how to build your code and run the tests.

Contribute

TODO: Explain how other users and developers can contribute to make your code better.

If you want to learn more about creating good readme files then refer the following guidelines. You can also seek inspiration from the below readme files:

• ASP.NET Core
• Visual Studio Code
• Chakra Core

npm

npm account

username: leandrofrancia
email: [e-mail] org: trii pass: Telefonia$

//////////////////////////////////// How to publish a scoped NPM package for your organization

Setting up your package and your terminal

1-Head to the package directory in your favoured terminal. 2-Once you’re there, double check your package.json has two important things:

Check the “name” field fits the following naming structure: @organization/your-package-name. It must contain the “@”, your organization name and the slash before your package name to correctly scope to your organization.

Check you’re happy with the package version number. This will be published alongside the content of your package on the NPM registry, and users of your package will be able to install this version by adding it to the end of their package install commands, such as: npm install @organization/your-package-name@1.2.3.

3-Run the command npm adduser in your terminal to log in to NPM. This will ensure you have the right permissions to publish your package in the next step.

4-Now run the command <<| npm publish --access public |>> to publish your package to the NPM registry.

////////////////////////////////////