How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
Im passionate about EcmaScript Modules and the removal of bundles in a HTTP 2 world. So I created didi to convert Common JS modules to EcmaScript Modules. It's still a work in progress and I'm looking for contributors.
Convert a project from common JS to ESmodules, with included bundler-like / task runner behaviour.
didi
A transpiler for JavaScript and Typescript, transforming CommonJS modules into distinct ES Modules
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.
constcolorThief=require('colorThief');// base specifier example, no paths needed
run didi path/to/example-project
The result should have output a new target directory within this example-project and also a server should have started on http://localhost:8086.
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:
importcolorThieffrom"color-thief";// still no path?
Im passionate about EcmaScript Modules and the removal of bundles in a HTTP 2 world. So I created didi to convert Common JS modules to EcmaScript Modules. It's still a work in progress and I'm looking for contributors.
adam-cyclones / didi
Convert a project from common JS to ESmodules, with included bundler-like / task runner behaviour.
didi
A transpiler for JavaScript and Typescript, transforming CommonJS modules into distinct ES Modules
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.
run
didi path/to/example-project
The result should have output a new target directory within this example-project and also a server should have started on
http://localhost:8086
. 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: