Who uses didi?
Frontend and deno developers will find didi useful.
Try it out.
didi is not ready for production however you can still take didi for a spin!
npm install -g @didi-js/client-didi-cli # or yarn global add @didi-js/client-didi-cli
Create a project an entry file, some installed node_modules and then require the browser dependency into your entry file using the base specifier.
const colorThief = require('colorThief'); // base specifier example, no paths needed
The result should have output a new target directory within this example-project and also a server should have started on
You may see some console errors in the browser, this is normal for this stage.
You may also notice that your import looks like this:
import colorThief from "color-thief"; // still no path? what wizardry is this!
didi also enables node.js style resolution with native ES Modules but right now didi genereates an importmap and optional ES Modules polyfil, even browsers that dont support ES Modules will support them in a didi project.
How it works:
- You can use the CLI to run didi.
- didi ships with an embedded custom TypeScript compiler.
- A complete starter project for the browser can be generated or for deno just the
- didi strives to generate minimal glue-code, but as of today, browsers that don't support import-maps will need the es_modules_polyfill (default), The positive side effect is that didi enables support for ES Modules in aging browsers, that includes dynamic import calls!
- A dev-server is provided to test your sources during the build, then finally serve a development environment.
- A dev-browser (headless browser) is used to prune all deps that were not actually used during the build step. A cache will be kept afterward, keeping build times down.
- Everything should work from then on. - but if it doesn't, PR's and issues welcome.
Building for development
To contribute to didi first lets get a copy of this repository setup.
git clone https://github.com/adam-cyclones/didi.git cd didi yarn install
didi is split into packages, there are two types of package, clients and libs, clients consume libs, for example
lib-didi and others.
Thanks to iterative work to improve developer experience, didi is controlled by didi-ops, everything is very simple to work with, run any of the package.json scripts (technically its just one script!) and then follow the prompts.
See our reasons for didi-ops which explains a little more about what, and why didi-ops.
At the root of this repository you can see a package.json file which controls all present and future packages didi-ops generates.
client-didi-cli is the only way to interact with didi, so you should start here.
The first time you setup for development you should do the following:
# didi-ops shadows the default `link` script - read about didi-ops scripts bellow. # run: yarn link # Answer the prompts by selecting: `client-didi-cli` # Then select all available packages yarn install-all yarn dev
client-didi-cli points to the
releases/lib-demo-project for development purposes, this allows tsc and node to compile and run on any changed packages. The example project is detailed by the
Try it out section.
|Script||(All scripts prompt for answers).|
|add||Generates a new package with sources, docs and release folders then builds this package, its a good starting point.|
|remove||Removes all traces of a didi package, however published packages remain published.|
|build||Builds clients and thier didi-lib dependencies.|
|dev||The same as build however it also watches for changes and executes the client based on args provided by
|version||Select packages to bump versions, either manually or by the github labels associated with this branch and issue.|
|publish||Select packages to publish, dry-run is available.|
|link||links libs together, or edits existing links then installs all node_modules for didi packages in source and release.|
|test||run all tests including those generated but
What to expect
The result of compilation should look a bit like this:
|File / Directory|
|target||didi output directory|
|es2015||we target es2015 until new specification land in the future|
|debug / release||debug is unoptimized and faster to build, release will optimize output for production|
|es_modules||This is where all your transpiled es_modules can be found,
|index.mjs||This will contain your project and imports based on the specified main of targeted projects package.json|
|index.html||The starting point of a didi frontend project, didi writes some glue code to allow a didi project to function|
|es-module-shims.min.js||Until importmaps are supported didi uses this polyfill by default but it can be turned off for bleeding-edge testing|
|didi.importmap||Used resolve your ES Modules with base specifiers and remain compatible with (ex) CommonJS (node resolution)|
packages/website-didi is a Docusaurus project in progress, we already have full support for the API Reference generated from Typedoc comments, for this reason we strive to provide high standards of doc comment coverage in everything we make.
http://didi.land will be the domain, we need as much support with the website as we do with the project itself, if your interested, reach out.
Want to help build the future of the web?
There is a growing list or tasks as didi heads for 1.0.0. Team didi:
- Adam Crockett
"We need your help, let's break away from bundlers, support didi"
- Do you want to join team didi or maybe leave us a star?
We want to build a collaborative open source community for didi; here are the actions the community decided so far.
- Vote: choose the name for didi, (formally unpack)
- Vote: choose the logo for didi
- Chat with Deno - Can we be dinosaurs too?
- AWS features didi in Open Source News!
- Logo by Adam Crockett
- दीदी - didi means sister, we are sister a too deno in the sense that we share similar goals, remove CommonJs packages and (for us, CommonJs bundles) from the equation and make packages widely available in a "Webby" way that conforms to EcmaScript standards.