Roadmap to v1, pt. 2

[iuioiua]

As discussed with Yoshiya, the tasks in #3489 are complete. This issue continues the roadmap for v1 of the Deno Standard Library. It focuses on lingering issues that would be good to have addressed by v1. Most of this list comes from the previous issue of @lino-levan's triage list.

The initial version of this list is rough but will be updated as needed. Opinions and concerns are welcome.

High priority

• tracking: complete documentation #3764
• tracking: improve test coverage #3713
• suggestion: rework std/log to use Streams API #3907
• tracking: enable noUncheckedIndexedAccess #4040

Medium priority

• possible bug: investigate std/crypto's vs old std/hash's digest() for large streams #3774
• tracking: cleanup deprecated APIs #3718

Low priority

• suggestion: centalise external dev dependencies #3795
• tracking: remove use of TypeScript enums #3782

To be prioritized from Lino's list...

• path.resolve depends on cwd #1136 - Maybe requires a breaking change to accomplish
• Allow Zip and Unzip to work on more than two arrays #1203 - Definitely requires a breaking change to accomplish
• Modernize std/archive/tar #1658 - This is stuck on upstream, which is super unlucky. I'd hate to stabilize any API that relies on readers.
• log: should expose global state #1826 - Looks like this is just a deeper sign that the logging we have right now is bad, we need to really think about this API imo.
• tracking: Deno streams to web streams conversion #1986 - Same as Modernize std/archive/tar #1658
• feat(encoding/csv): restructure proposal #2291 - Requires breaking changes
• bug(flags): boolean flag doesn't equal assigned value #2341 - See above
• bug(flags): collect is prioritised over boolean #2342 - See above
• flags: Skip parsing numeric-looking argument with no option #2370 - See above
• Separate logging information from presentation #2398 - Another complaint about the logging module
• Path: Should normalize() remove trailing slashes? #2441 - Probably need to come up with a decision on this one
• Rework ConsoleHandler to use native console methods #2645 - Yet another logging complaint
• fix(encoding/csv): remove stringify object array support #2660
• proposal: Move std/flags to std/cli #3526 - Sentiment seems mixed, we could always drop this
• assertEquals conflicts with the JavaScript's meaning of "equality" #3513 - Might require breaking changes
• Default log level for getLogger should be "WARNING" #3508 - Another logging complaint
• Grouping data format modules under one namespace #3462 - I agree in concept, but in practice it feels unlikely that this happens
• [http/cookie] Add support for adding "Cookie" header #3326 - May require breaking changes to naming
• JSON support in loggers #3394 - Another logging complaint
• Suggestion: deprecate the unzip function in favor of the zip function #3407
• fs.walk() should return relative paths, not absolute paths. #3456 - Probably a breaking change
• testing/bdd.ts with flat test grouping style the only option scoped to top level test instead of the file #2096
• "assertSnapshot" should add support for wildcards #2147
• dotenv: different behaviour between load.ts and mod.ts when used together with run --watch= #2490
• WASI: Make the module, browser compatible #2745
• testing: bdd ".only" option might not work #2979
• bdd testing: easy testing of arrays #3268
• abortableAsyncIterable() should call .return() on the generator once aborted #3518
• std/jsonc seems to strip comments  #3502
• Yaml library drops comments when round tripping #3307
• Assertion library custom message should still allow for inclusion of values #878 - probably a good thing to think about
• Suggestion: Support X509Certificate within hash module #981 - slightly out of date, probably needs some love
• Add lookPath function to find the path of an executable #1056 - I'm gonna pick this one up
• std/fs/move should handle moving across mounts/devices #1070 - Probably gets resolved by fix(fs): support rename across filesystems deno#19879 but I don't think that one will land
• collections: most functions that work on Record do not work with interface #1126 - This should just be closed imo
• Concept Proposal: std/http/middleware #1295 - Probably just a "no"
• std/flags should be able to provide "--help" usage information #1586 - @kt3k seems to be -1 on making flags more complicated than it currently is, probably needs an update
• A way to check std when converted to working under Node.js via dnt #1918 - would still be nice to have
• feat: abstraction of ffi api libraries loading #1968 - pretty strongly against this one, we should probably make a decision
• Support the Response object in assertObjectMatch #2204 - I'm not a fan of this one, probably just needs a "no"
• suggestion: getAvailablePort() #3279 - needs to be broken down into separate issues
• add jwt module in std #3290 - probably needs a "no"

[iuioiua]

Closing this issue in favor of #4600, which more clearly defines the roadmap to stabilization.