You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To begin, I wanted to thank you all for all the time, energy, and effort spent in building this runtime and community. This has easily been the best developer experience I’ve ever had, from writing code, asking questions, to getting to meet new people.
Before I discuss my request, I should introduce the reason I’m here. After discovering the way Deno’s import system works (and seeing the benefits of this method) I set to work on building a decentralized module registry and CDN. My team and I built something that prevents modules from ever being modified with malicious intent and/or leaving the web as a whole. We’ve seen an immense amount of positive community feedback since launch about a month ago, and we have permanently published over 14,500 files with almost 60 modules on the platform to date! I wanted to get some opinions/permission on a request that is becoming increasingly relevant from within our community: Will Deno Standard Modules be supported on the platform?
This leads me to ask: Would you all permit us to create a repository in our organization with a submodule inside that points to this repository? From this, we could set up CI to automatically publish the standard modules to the platform whenever a new release is made.
I’m mainly concerned to be asking this because I don’t want our platform to seem like a parasite to your ecosystem, but at the same time, if GitHub has a temporary outage, our tools wouldn’t work for new developers who don’t have cached modules.
Feel free to leave opinions, questions, and concerns. We’re in favor of whatever you all believe is best for the Deno community!
Tate
The text was updated successfully, but these errors were encountered:
Hello Deno maintainers!
To begin, I wanted to thank you all for all the time, energy, and effort spent in building this runtime and community. This has easily been the best developer experience I’ve ever had, from writing code, asking questions, to getting to meet new people.
Before I discuss my request, I should introduce the reason I’m here. After discovering the way Deno’s import system works (and seeing the benefits of this method) I set to work on building a decentralized module registry and CDN. My team and I built something that prevents modules from ever being modified with malicious intent and/or leaving the web as a whole. We’ve seen an immense amount of positive community feedback since launch about a month ago, and we have permanently published over 14,500 files with almost 60 modules on the platform to date! I wanted to get some opinions/permission on a request that is becoming increasingly relevant from within our community: Will Deno Standard Modules be supported on the platform?
This leads me to ask: Would you all permit us to create a repository in our organization with a submodule inside that points to this repository? From this, we could set up CI to automatically publish the standard modules to the platform whenever a new release is made.
I’m mainly concerned to be asking this because I don’t want our platform to seem like a parasite to your ecosystem, but at the same time, if GitHub has a temporary outage, our tools wouldn’t work for new developers who don’t have cached modules.
Feel free to leave opinions, questions, and concerns. We’re in favor of whatever you all believe is best for the Deno community!
Tate
The text was updated successfully, but these errors were encountered: