ProtoLibBerkay

This library aims to use a declaration file converted into "example.d.ts" file from Protobuf files in the package. This library was generated with Angular CLI Version 16.1.0.

Features

Makes the integration of Protobuf into your Typescript projects easier.

Why do we intend to do this?

The reason we aim to do this is to be able to more quickly compare the input entered by an external factor and whether the type in our protobuf file is the same (Protobuf files run faster than other type definition files). For example, if a value other than the specified type is given to the takeValue function, our program will throw an error.

Build

Run ng build proto-lib to build the project. The build artifacts will be stored in the dist/ directory.

Publishing

Before you publish your library, ensure you are logged in to the correct account. If you aren't, use the npm login command. After successfully building your library with ng build proto-lib-berkay, navigate to the dist folder using cd dist/proto-lib-berkay and then run npm publish to make your library public.

Usage

To implement the ProtoLibBerkay package in a project, input the npm install proto-lib-berkay command in your terminal. You can then import the entire library by using import * as TheNameUChose from 'proto-lib-berkay'; or import a specific object, such as import {ProtoLibService} from 'proto-lib-berkay';.

Get the desired version.

If you aim to utilize the most recent version of a library, start by uninstalling the existing library. To do so, use the command npm uninstall proto-lib-berkay. Subsequently, verify its successful removal before you proceed to reinstall it. To ensure you fetch the latest available version, reinstall the library using npm install proto-lib-berkay. However, if you wish to install a specific version of the library, you can do so explicitly. Use the command npm install proto-lib-berkay@DesiredVersion, substituting 'DesiredVersion' with the version number you prefer.

Footnote

This package uses Semantic Versioning, meaning version numbers should follow a MAJOR.MINOR.PATCH format, such as 1.0.2. If you've made significant changes (breaking changes), increment the MAJOR version. If you've added minor features, increment the MINOR version. And if you've only made bug fixes, increment the PATCH version (I manually update the version numbering within the package when there is a version change). Sometimes even though I change it manually, the version is not transferred to the dist side, then I have to enter it from the dist file, and please make changes from the packages on the library file, because this is the part we build.