As much as I love open-source, not every project or package is meant to become open-source. Especially commercial projects are usually not released under an open-source license. For these cases you can use:
Private NPM/yarn packages with a license defined as "UNLICENSED" should do the trick. Make sure to not confuse it the "UNLICENSE", which is open-source.
Private composer packages can use the license key "proprietary" to avoid issues.
That's it. More a public note here than an article, but I guess that's fine.
Other articles of mine that you might like
- Personal Discovery Journey Into Code-World: FaaSD and OpenFaaS
- Thank me later: How to install PHP ext-intl in docker on Alpine Linux
- Common Issues using Laravel Websockets with beyondcode/laravel-websockets
- PHPScraper and Python3 BeautifulSoup in Comparison
- How to Upgrade Your Node Versions on Linux Development Machines and Keep up to Date
Top comments (2)
But a very good note, sometimes the work demands to have our rutines as private for the collaborators (for use and even edit the code).
In this case, i want to publish some react components to npm, but they are not 'free to use' unless all the colaborators agree that person uses it or whatever to do with him.
I dont wanna configure tokens for every project that uses it in order have it on the node_modules folder, instead just warning that the code its just for me or allowed people...
Thanks man!