У нас вы можете посмотреть бесплатно Setup New GitHub Repository | Building an NPM Package with TypeScript или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
It is not complicated in itself to initialize a repository but GitHub has introduced a lot of new features, and new best practices they would love you to follow. On the page to create a new repository, we can choose the name, the type of repository (public or private), add a README, a gitignore file and a license. / create-a-new-github-repository-building-a-... Name and repository visibility The name of a package in npm has to be lowercase. I would recommend you add the same name for the repository. A repository is often public when you want to create a public npm package. You can have private npm packages but for this series of articles, we will create a public one. The code will be visible by all, and your users can file issues, and eventually contribute to your project, create pull requests to add features and fix bugs. gitignore Adding a gitignore file on this page will let you choose between multiple types of projects. A gitignore file contains the list of files that git should ignore when you commit and push to your repository. You can create this file yourself and add the path of the files you want to ignore. You don’t have to use one that is on the list. I would though recommend that you do, and you choose the Node gitignore. The Node gitignore contains common files that are generated by plugins, build tools and needs to be ignored. If you create the gitignore from scratch, you might miss some. And there is no reason to not take advantage of what the community has already done. You can always modify the Node gitignore after. Licensing Next, we can choose a license. The reason why a license is important for any project is because it acts as a legal document that indicates the permissions that you give to other developers, companies on your project. So you will have licenses that will allow developers to use the project commercially, for profit, or will restrain the usage for non profit. Depending on what license you choose, some companies might unauthorised their developers to use your project.