Closed jbenet closed 10 years ago
Ok this is done. Transformer was broken down into a set of modules, see below. Turns out you can just use any conversions directly. Dynamic resolution is the only thing the main tool/lib does. This means two main workflows emerge:
In your code:
transformer
cli to install, resolve, and/or compile conversion modulesIn cli / repl:
transform
cli to convert directly. it does dynamic resolution.require('dat-transformer')
in repl to convert with dynamic resolution.Feedback on all this very welcome. I'll close this issue but feel free to comment in this new design here, or open another issue.
(from the README)
Transformer's core is modular itself. See:
transformer
- utility to install, resolve, and compile transformer modulestransform <types> < <infile> > <outfile>
- expose any transformer as a pipe-loving unix utilityFor making your own types and conversions:
transformer-pkg
)Other:
talking with @maxogden, decided to move dynamic loading to another module. So it will work like this:
transformer
core + clitransformer-resolution
module to resolve conversion pathstransformer-dynamic
core api with dynamic string -> module resolution + loading