Dynamic Module Services

I think that dynamic module resolution and loading is the future of the javascript/typescript/wasm world. It eliminates the need for storing generated code since it can be resolved and loaded/compiled on the fly. Platforms like deno are already using similar techniques to load in javascript/typescript over https/http during runtime.

Project Goals

This project was created with several goals in mind.

Standarization

The main problem with existing dynamic import resolution/loading systems is that they lack standardization of configuration/functionality. This project aims to solve this issue by standardizing end user configuation and seperating implementation from configuration. Platforms should be able to implement dynamic resolution how they need to without limiting the ability for end users to configure it for their needs.

Extensiablity

Currently most existing implementations of dynamic module resolution/loading cannot be extended without making changes to the original implmentation(With the exception of being able to remap paths). If an end user wants to load a code from a gist or a git repository or even an originazations internal service for sharing common code, they should be able to do so without modifying the platform code.

Collaboration

The intrest around the idea of really taking advantage of the module resoltion system has been growing, but it lacks any specific direction. This is an idea that really only needs to get a critical mass of those intrested in the same place. Once organized it should be easy for a community or supporters to flesh out a system, and implement the result anywhere they see fit.

Getting started

Examples are in the examples folder. Nothing is final yet so if you have an idea for a feature or change open an issue.

Contributing

Install npm packages.

1. yarn install

That's it your ready to contribute.