Archive the repo
UltiRequiem opened this issue · comments
Since this is now part of the std,
https://github.com/pietvanzoen/deno-dotenv#-dotenv-is-now-a-part-of-deno_std-
It would help if this repo is archived, so is more clear that we should prefer using std/dotenv than this.
Makes sense. I've been meaning to drop into the existing issues here and direct people to the std lib. Archiving prevents comments on issues so I'll take care of that first.
Hi @pietvanzoen hope you're well and haven't faded from Open Source. Hopefully you're just on a brief holiday from dealing with the constant demands of random strangers... like me. :)
Rather than open a new issue I thought I would just add to this one. I am new-ish to Github and also to Deno in that I only get to poke at this stuff every second weekend or so. But my request is probably something I could do, if you like, as it's just text editing. Let me know if I should give it a shot as my first PR on Github:
As a noob to Deno and Deno Deploy, and as someone who'd never used Node either, navigating the mazes of old docs around environment variables in multiple ecosystems cost me a half day last month, and I was pretty embarrassed when I finally clued I to how easy it really was... if only I had found the right docs/links first.
It's great that this repo is now std but and yes that is in the README but it is not apparent on the leader board here:
...and I think it should be. Check out media_types just 2 items above it... I strongly feel this edit would help many more new adopters like me.
Never underestimate my -- er, our -- ability to get lost in the weeds. :)
Is it time, and is it possible, for this report to look / act more like media_types ? If so I could give it a shot... see the general differences below.
Hey folks. Apologies for going incognito for a while there. My wife and I just had our 2nd child so it's been difficult to prioritise this stuff. 😛
Will archive the project now.
So long and thanks for all the fish.