Intrinsic Planning

[sgammon]

We'd like to implement enough Node intrinsics that Elide can be used with most Node libraries. At the moment, we're like halfway to supporting the full Fetch API, and basic functionality like URL, JSON, and btoa/atob is implemented and working. What follows is a list of intrinsic APIs we should implement next:

• Web Standards
  • Console API: Implemented
  • URL API: Implemented
  • Web Streams API: Half implemented
  • Fetch API: Half-implemented
  • Web Crypto API: In-progress as of alpha4
  • Subtle Crypto API: Needed for standards-compliant crypto
• Node APIs
  • Node Buffer API: Implemented (Polyfill)
  • Node Streams API: Implemented (Polyfill)
  • Node Event Emitter API: Implemented (Polyfill)
  • Node Crypto API: Only a subset of these, for example randomFill et al.
  • Node HTTP API: Lower-level integration than Express API, supported as of alpha4
  • Node Filesystem API: Implement VFS bridge
  • Node Zlib API: Ideally with native zlib
• Server APIs
  • Express API: Initial support for servers implemented in Express
    • Router bindings / bridge
    • Parameter bindings

[sgammon]

This issue is being retired in favor of API Conformance