![\"Travis](\"https://img.shields.io/travis/com/bevry/make-deno-edition/master.svg\")
\n![\"NPM](\"https://img.shields.io/npm/v/make-deno-edition.svg\")
\n![\"NPM](\"https://img.shields.io/npm/dm/make-deno-edition.svg\")
\n![\"Dependency](\"https://img.shields.io/david/bevry/make-deno-edition.svg\")
\n![\"Dev](\"https://img.shields.io/david/dev/bevry/make-deno-edition.svg\")
\n![\"GitHub](\"https://img.shields.io/badge/github-donate-yellow.svg\"){kind=icon}
\n![\"Patreon](\"https://img.shields.io/badge/patreon-donate-yellow.svg\"){kind=icon}
\n![\"Flattr](\"https://img.shields.io/badge/flattr-donate-yellow.svg\"){kind=icon}
\n![\"Liberapay](\"https://img.shields.io/badge/liberapay-donate-yellow.svg\"){kind=icon}
\n![\"Buy](\"https://img.shields.io/badge/buy%20me%20a%20coffee-donate-yellow.svg\"){kind=icon}
\n![\"Open](\"https://img.shields.io/badge/open%20collective-donate-yellow.svg\"){kind=icon}
\n![\"crypto](\"https://img.shields.io/badge/crypto-donate-yellow.svg\"){kind=icon}
\n![\"PayPal](\"https://img.shields.io/badge/paypal-donate-yellow.svg\"){kind=icon}
\n![\"Wishlist](\"https://img.shields.io/badge/wishlist-donate-yellow.svg\"){kind=icon}
\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/badges\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a ts file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically by your own deno compatible editions.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically by your own deno compatible editions.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/links\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/typechecker\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/start-of-week\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/start-of-week\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n- https://github.com/bevry/ambi\n- https://github.com/bevry/arrangekeys\n- https://github.com/bevry/badges\n- https://github.com/bevry/binaryextensions\n- https://github.com/bevry/cachely\n- https://github.com/bevry/detect-indentation\n- https://github.com/bevry/envfile\n- https://github.com/bevry/errlop\n- https://github.com/bevry/fellow\n- https://github.com/bevry/get-cli-arg\n- https://github.com/bevry/ignorefs\n- https://github.com/bevry/ignorepatterns\n- https://github.com/bevry/istextorbinary\n- https://github.com/bevry/links\n- https://github.com/bevry/memo\n- https://github.com/bevry/native-promise-pool\n- https://github.com/bevry/normalify\n- https://github.com/bevry/oneday\n- https://github.com/bevry/remove-indentation\n- https://github.com/bevry/sortobject\n- https://github.com/bevry/start-of-week\n- https://github.com/bevry/textextensions\n- https://github.com/bevry/trim-indentation\n- https://github.com/bevry/typechecker\n- https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\nHere is a list of Bevry packages that have used `make-deno-edition` to make themselves compatible with deno:\n\n1. https://github.com/bevry/ambi\n1. https://github.com/bevry/arrangekeys\n1. https://github.com/bevry/badges\n1. https://github.com/bevry/binaryextensions\n1. https://github.com/bevry/cachely\n1. https://github.com/bevry/detect-indentation\n1. https://github.com/bevry/envfile\n1. https://github.com/bevry/errlop\n1. https://github.com/bevry/fellow\n1. https://github.com/bevry/get-cli-arg\n1. https://github.com/bevry/getsetdeep\n1. https://github.com/bevry/ignorefs\n1. https://github.com/bevry/ignorepatterns\n1. https://github.com/bevry/istextorbinary\n1. https://github.com/bevry/links\n1. https://github.com/bevry/memo\n1. https://github.com/bevry/native-promise-pool\n1. https://github.com/bevry/normalify\n1. https://github.com/bevry/oneday\n1. https://github.com/bevry/remove-indentation\n1. https://github.com/bevry/ropo\n1. https://github.com/bevry/sortobject\n1. https://github.com/bevry/start-of-week\n1. https://github.com/bevry/textextensions\n1. https://github.com/bevry/trim-indentation\n1. https://github.com/bevry/typechecker\n1. https://github.com/bevry/valid-module\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### Prerequisites\n\nYou will be running `make-deno-edition` on a npm package that is written in TypeScript and uses ESM.\n\nAny imports from your package must either:\n\n- be a relative import, that has a corresponding `.ts` file\n- be a URL that a resolves to a `.ts` file (typical deno style)\n- be a dependency that has a `package.json` file, that contains a `deno` entry field, or a `main` field that has a corresponding `.ts` file\n- where a custom package entry was used, there is a corresponding `.ts` file, or a `deno` edition in the `package.json` file such that the deno entry can be inferred\n\nIf you import a package that is not compatible with deno, but does have source code written in TypeScript using ESM, then fork the imported package, run through the instructions below to generate the deno comptible edition for it, then submit a pull request, so that it has a deno compatible edition, and thus can be used automatically in the future.\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them.\n\n### API\n\nAPI usage of `make-deno-edition` is to come.\n\n\n\nnpm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from ./file.ts` and `import thing from https://unpkg.com/badges@^4.13.0/edition-deno/index.ts`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from https://unpkg.com/dep@^1.0.0/file.ts`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and instantly applies the following changes to create a compatible deno edition in a `deno-edition` directory:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n### Extras\n\n#### `README.md` instructions\n\nInside the `README.md` file, you should instruct Deno-only users of your package about your Deno entry point, you can do this by instructing them to use the CDN URL and entry for your package:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from ./file.ts` and `import thing from https://unpkg.com/badges@^4.13.0/edition-deno/index.ts`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from https://unpkg.com/dep@^1.0.0/file.ts`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and instantly applies the following changes to create a compatible deno edition in a `deno-edition` directory:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n### Extras\n\n#### `README.md` instructions\n\nInside the `README.md` file, you should instruct Deno-only users of your package about your Deno entry point, you can do this by instructing them to use the CDN URL and entry for your package:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from ./file.ts` and `import thing from https://unpkg.com/badges@^4.13.0/edition-deno/index.ts`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from https://unpkg.com/dep@^1.0.0/file.ts`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and instantly applies the following changes to create a compatible deno edition in a `deno-edition` directory:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js with Require for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMake a deno edition of a npm package\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from ./file.ts` and `import thing from https://unpkg.com/badges@^4.13.0/edition-deno/index.ts`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from https://unpkg.com/dep@^1.0.0/file.ts`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and instantly applies the following changes to create a compatible deno edition in a `deno-edition` directory:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from ./file.ts` and `import thing from https://unpkg.com/badges@^4.13.0/edition-deno/index.ts`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from https://unpkg.com/dep@^1.0.0/file.ts`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and instantly applies the following changes to create a compatible deno edition in a `deno-edition` directory:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from ./file.ts` and `import thing from https://unpkg.com/badges@^4.13.0/edition-deno/index.ts`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from https://unpkg.com/dep@^1.0.0/file.ts`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from ./file.ts` and `import thing from https://unpkg.com/badges@^4.13.0/edition-deno/index.ts`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from https://unpkg.com/dep@^1.0.0/file.ts`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from https://unpkg.com/dep@^1.0.0/file.ts`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is a list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a write(chunk: any): any method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mappedd to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are checked to see if they have a `deno` field in their `package.json` denoting where to look for the deno compatible entry file, or if their `main` field in the `package.json` ends with `.ts` then it is assumed to be deno compatible\n\n 1. so the more dependencies that `make-deno-edition` is run on, then the more dependents that can become compatible with deno\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\nUnlike Node.js and TypeScript, which supports unresolved paths, e.g. `import thing from './file'` and `import thing from './'`, Deno only supports resolved paths, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM). This is because Deno has no conception of `package.json`.\n\nUnlike Node.js and TypeScript, which supports `package.json` to specify dependency versions so you can just do `import dep from 'dep'`, instead Deno has no conception of `package.json`, so all dependencies must be imported via their CDN URL with reference to their version number, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\nDeno and Node.js different on their APIs. Several Node.js builtins can be aliases to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nAnd in the end, you need to hope your dependencies are also compatible with Deno.\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `deno-edition` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 14 with Require for modulesmake-deno-edition/edition-node-esm/index.js is TypeScript compiled against ESNext for Node.js with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 10 || 12 || 14 || 15 with Require for modulesmake-deno-edition/edition-esnext-esm/index.js is TypeScript compiled against ESNext for Node.js 12 || 14 || 15 with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 10 || 12 || 14 || 15 with Require for modulesmake-deno-edition/edition-esnext-esm/index.js is TypeScript compiled against ESNext for Node.js 12 || 14 || 15 with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 10 || 12 || 14 || 15 with Require for modulesmake-deno-edition/edition-esnext-esm/index.js is TypeScript compiled against ESNext for Node.js 12 || 14 || 15 with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 10 || 12 || 14 || 15 with Require for modulesmake-deno-edition/edition-esnext-esm/index.js is TypeScript compiled against ESNext for Node.js 12 || 14 || 15 with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 10 || 12 || 14 || 15 with Require for modulesmake-deno-edition/edition-esnext-esm/index.js is TypeScript compiled against ESNext for Node.js 12 || 14 || 15 with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 10 || 12 || 14 || 15 with Require for modulesmake-deno-edition/edition-esnext-esm/index.js is TypeScript compiled against ESNext for Node.js 12 || 14 || 15 with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-esnext/index.jsmake-deno-edition/edition-esnext/index.js is TypeScript compiled against ESNext for Node.js 10 || 12 || 14 || 15 with Require for modulesmake-deno-edition/edition-esnext-esm/index.js is TypeScript compiled against ESNext for Node.js 12 || 14 || 15 with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n![\"Status](\"https://github.com/bevry/make-deno-edition/workflows/bevry/badge.svg\"){kind=icon}
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n#### Interactive\n\nThese are some highlighted packages that have interactive examples for the different targets they support, and whose compatibility for Deno was provided automatically by make-deno-editions, illustrating how easy multi-target production and consumption is of write-once packages.\n\n- [Caterpillar](https://github.com/bevry/caterpillar) is a logging library for Deno, Node.js and Web Browsers, it will pipe to anything that has a `write(chunk: any): any` method.\n - [Source Directory](https://github.com/bevry/caterpillar/tree/master/source)\n - [Deno Example](https://repl.it/@balupton/caterpillar-deno)\n - [Node.js Example](https://repl.it/@balupton/caterpillar-node)\n - [Web Browser Example](https://repl.it/@balupton/caterpillar-browser)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `std/node` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relativeu path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported if:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they have a `main` field in the `package.json` that ends with `.ts` (is a typescript file), then it is assumed to be deno compatible\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/globals.html)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-es2020/index.jsmake-deno-edition/edition-es2020/index.js is TypeScript compiled against ES2020 for Node.js 10 || 12 || 14 with Require for modulesmake-deno-edition/edition-es2020-esm/index.js is TypeScript compiled against ES2020 for Node.js 12 || 14 with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n![\"ThanksDev](\"https://img.shields.io/badge/thanksdev-donate-yellow.svg\"){kind=icon}
\n\n\n\n\n\n\n![\"Discord](\"https://img.shields.io/discord/1147436445783560193?logo=discord&label=discord\")
\n![\"Twitch](\"https://img.shields.io/twitch/status/balupton?logo=twitch\")
\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `node:*` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported by:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file, then it's direct unpkg URL will be used.\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they are an installed dependency, their esm.sh URL will be used.\n\n 3. If they are an uninstalled dependency, the `npm:` prefix will be used.\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-es2022/index.jsmake-deno-edition/edition-es2022/index.js is TypeScript compiled against ES2022 for Node.js 18 || 20 || 21 with Require for modulesmake-deno-edition/edition-es2022-esm/index.js is TypeScript compiled against ES2022 for Node.js 18 || 20 || 21 with Import for modulesmake-deno-edition/edition-types/index.d.ts is TypeScript compiled Types with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `node:*` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported by:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file, then it's direct unpkg URL will be used.\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they are an installed dependency, their esm.sh URL will be used.\n\n 3. If they are an uninstalled dependency, the `npm:` prefix will be used.\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-es2022/index.jsmake-deno-edition/edition-es2022/index.js is TypeScript compiled against ES2022 for Node.js 18 || 20 || 21 with Require for modulesmake-deno-edition/edition-es2022-esm/index.js is TypeScript compiled against ES2022 for Node.js 18 || 20 || 21 with Import for modulesmake-deno-edition/edition-types/index.d.ts is TypeScript compiled Types with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `node:*` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported by:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file, then it's direct unpkg URL will be used.\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they are an installed dependency, their esm.sh URL will be used.\n\n 3. If they are an uninstalled dependency, the `npm:` prefix will be used.\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n npm install --global make-deno-editionmake-deno-editionnpm install --save make-deno-editionnpx make-deno-editionimport * as pkg from ('make-deno-edition')const pkg = require('make-deno-edition')This package is published with the following editions:
\n\nmake-deno-edition/source/index.ts is TypeScript source code with Import for modulesmake-deno-edition aliases make-deno-edition/edition-es2022/index.jsmake-deno-edition/edition-es2022/index.js is TypeScript compiled against ES2022 for Node.js 21 with Require for modulesmake-deno-edition/edition-es2022-esm/index.js is TypeScript compiled against ES2022 for Node.js 21 with Import for modulesmake-deno-edition/edition-types/index.d.ts is TypeScript compiled Types with Import for modulesHISTORY.md file.\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCONTRIBUTING.md file.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `node:*` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported by:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file, then it's direct unpkg URL will be used.\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they are an installed dependency, their esm.sh URL will be used.\n\n 3. If they are an uninstalled dependency, the `npm:` prefix will be used.\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n \n\n\n\n\n\n\n\n\n#### Sponsors\n\n- [Andrew Nesbitt](https://nesbitt.io) — Software engineer and researcher\n- [Balsa](https://balsa.com) — We're Balsa, and we're building tools for builders.\n- [Codecov](https://codecov.io/) — Empower developers with tools to improve code quality and testing.\n- [Poonacha Medappa](https://poonachamedappa.com)\n- [Rob Morris](https://github.com/Rob-Morris)\n- [Sentry](https://sentry.io) — Real-time crash reporting for your web apps, mobile apps, and games.\n- [Syntax](https://syntax.fm) — Syntax Podcast\n\n#### Donors\n\n- [Andrew Nesbitt](https://nesbitt.io)\n- [Balsa](https://balsa.com)\n- [Chad](https://opencollective.com/chad8)\n- [Codecov](https://codecov.io/)\n- [entroniq](https://gitlab.com/entroniq)\n- [Jean-Luc Geering](https://github.com/jlgeering)\n- [Michael Duane Mooring](https://bevry.me)\n- [Mohammed Shah](https://github.com/smashah)\n- [Poonacha Medappa](https://poonachamedappa.com)\n- [Rob Morris](https://github.com/Rob-Morris)\n- [Sentry](https://sentry.io)\n- [ServieJS](https://github.com/serviejs)\n- [Skunk Team](https://skunk.team)\n- [Syntax](https://syntax.fm)\n\n\n\n\n\n## License\n\nUnless stated otherwise all works are:\n\n- Copyright © [Benjamin Lupton](https://balupton.com)\n\nand licensed under:\n\n- [Artistic License 2.0](http://spdx.org/licenses/Artistic-2.0.html)\n\n\n","readmeFilename":"README.md","gitHead":"8bf83148bea3b04dde36798626c1774962bc0d40","_nodeVersion":"20.10.0","_npmVersion":"10.2.3","dist":{"integrity":"sha512-XmR8DymYLH6kzQtPvWo6KAfdoGy4MuinY9vj2kI8V72PwuVb0vf/NWzntAPPCKlt9ry+wcEDkb2faPnDRSe4zA==","shasum":"5c0cddb4a67ce7d7071797bb545541bdf8160fd6","tarball":"https://registry.npmjs.org/make-deno-edition/-/make-deno-edition-2.2.0-next.1703696930.8bf83148bea3b04dde36798626c1774962bc0d40.tgz","fileCount":24,"unpackedSize":106633,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDKHrLoEvW9bo+EepFANvdL4NBgWD8Qe1u/o5gHLVjHFQIgaOk4XKW4NfH9o1qjiI/Zvp+n09XFfcyQzh6V+kQngWE="}]},"_npmUser":{"name":"bevryme","email":"us@bevry.me"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/make-deno-edition_2.2.0-next.1703696930.8bf83148bea3b04dde36798626c1774962bc0d40_1703696932204_0.9637169255058178"},"_hasShrinkwrap":false},"2.2.0":{"name":"make-deno-edition","version":"2.2.0","license":"Artistic-2.0","description":"Automatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.","homepage":"https://github.com/bevry/make-deno-edition","funding":"https://bevry.me/fund","repository":{"type":"git","url":"git+https://github.com/bevry/make-deno-edition.git"},"bugs":{"url":"https://github.com/bevry/make-deno-edition/issues"},"keywords":["denoify","edition","editions","es2022","node","npm","transpile","typed","types","typescript","unpkg"],"badges":{"list":["githubworkflow","npmversion","npmdownloads","---","githubsponsors","thanksdev","patreon","liberapay","buymeacoffee","opencollective","crypto","paypal","---","discord","twitch"],"config":{"githubWorkflow":"bevry","githubSponsorsUsername":"balupton","thanksdevGithubUsername":"bevry","buymeacoffeeUsername":"balupton","cryptoURL":"https://bevry.me/crypto","flattrUsername":"balupton","liberapayUsername":"bevry","opencollectiveUsername":"bevry","patreonUsername":"bevry","paypalURL":"https://bevry.me/paypal","wishlistURL":"https://bevry.me/wishlist","discordServerID":"1147436445783560193","discordServerInvite":"nQuXddV7VP","twitchUsername":"balupton","githubUsername":"bevry","githubRepository":"make-deno-edition","githubSlug":"bevry/make-deno-edition","npmPackageName":"make-deno-edition"}},"author":{"name":"Benjamin Lupton","email":"b@lupton.cc","url":"https://balupton.com"},"authors":["Benjamin Lupton \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAutomatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.\n\n\n\n\n## Overview\n\n### Examples\n\n[Here is the growing list of all the packages that make-deno-edition has made compatible with Deno.](https://www.npmjs.com/search?q=keywords:deno-entry)\n\n### The Need\n\n**Node.js and TypeScript support unresolved paths**, e.g. `import thing from './file'` and `import thing from './'`. **Deno however, only supports resolved paths**, e.g. `import thing from './file.ts'` and `import thing from 'https://unpkg.com/badges@^4.13.0/edition-deno/index.ts'`. This means that anything imported into Deno must be directly resolvable and must use ECMAScript Modules (ESM).\n\n**Node.js and TypeScript support `package.json` files** to specify dependency versions, which enables code like `import dep from 'dep'`. **Deno however, has no conception of `package.json`**, so all dependencies must be imported via a directly resolvable CDN URL, e.g. `import dep from 'https://unpkg.com/dep@^1.0.0/file.ts'`.\n\n**Deno and Node.js different on their APIs**. Node.js builtins can be converted to Deno's `std/node` builtins, however several things such as `__filename`, `__dirname` require a polyfill, and other things have no direct compatibility so require different entries.\n\nIn the end, **you must hope your dependencies are also compatible with Deno.**\n\n### The Solution\n\nmake-deno-edition is a CLI tool that takes your source edition (whichever directory contains your package's typescript source files) and creates a compatible deno edition in a `edition-deno` directory.\n\nIt provides this compatibility by providing the following transformations:\n\n1. bultin imports (e.g. `fs`) are mapped to their corresponding deno `node:*` polyfill\n\n1. certain globals (e.g. `__filename` and `__dirname`) are mapped to their corresponding deno userland polyfilll\n\n1. internal imports (any relative path to another file inside your source edition) are mapped to their typescript file, e.g. `import thing from './file'` and `import thing from './file.js'` becomes `import thing from './file.ts`\n\n1. remote imports (e.g. any URL) are assumed to be compatible, as node.js doesn't support them, so it is assumed they are already deno compatible\n\n1. dependency imports (e.g. any package you install into node_modules) are supported by:\n\n 1. If they have a `deno` field in their `package.json`, which will denote where to look for the deno compatible entry file, then it's direct unpkg URL will be used.\n\n The more dependencies that `make-deno-edition` is run on, then the more dependencies will automatically have a `deno` entry field, and thus the more dependencies will be automatically compatible with Deno, enabling more dependents to be automatically compatible with Deno.\n\n 2. If they are an installed dependency, their esm.sh URL will be used.\n\n 3. If they are an uninstalled dependency, the `npm:` prefix will be used.\n\nmake-deno-edition will also intelligently ignore compatibility for files that are not essential, such as your test and utility files, but fail if compatibility for an essential file, such as an entry file and its required modules fail\n\nFinally, make-deno-edition will also update your `package.json` file with the details for the deno entry file, as well as the deno edition metadata, such that other packages and toolchains can make use of your deno compatibility.\n\n## Usage\n\n[Complete API Documentation.](http://master.make-deno-edition.bevry.surge.sh/docs/)\n\n### Preparation\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nIf you haven't already done so, add the following [editions](https://editions.bevry.me) metadata to your `package.json` file:\n\n```json\n \"editions\": [\n {\n \"description\": \"TypeScript source code with Import for modules\",\n \"directory\": \"source\",\n \"entry\": \"index.ts\",\n \"tags\": [\n \"typescript\",\n \"import\"\n ],\n \"engines\": false\n }\n ]\n```\n\nMake sure that the `directory` is where the source files are located, in the above example, they are located in a `source` directory, as it is with this repository.\n\nMake sure that the `entry` is where the entry file is located within the edition directory, in the above example, the entry is `index.ts`, as it is with this repository.\n\n### Executable\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate deno compatibility for your npm package, then you can skip this step.\n\nInstall `make-deno-edition` to your development dependencies using:\n\n```bash\nnpm install --save-dev make-deno-edition\n```\n\nThen add a `compile` npm script to your `package.json` containing:\n\n```\nmake-deno-edition --attempt\n```\n\nAlternatively, you can run it directly on your project via:\n\n```\nnpx make-deno-edition --attempt\n```\n\nThe `--attempt` flag will not emit a failure exit code if the deno edition generation was not successful. If you require a deno edition to be published, remove the `--attempt` flag.\n\n### Publishing\n\n> If you are using [`boundation`](https://github.com/bevry/boundation) to automatically generate compatible editions (web browsers, deno, multiple node.js versions) for your npm package, then you can skip this step.\n\n> If you are using [`projectz`](https://github.com/bevry/projectz) to automatically generate your `README.md` content, then you can skip this step.\n\nIf a deno edition was successfully created, it will be located in the `edition-deno` directory with the metadata added to the `editions` array in your `package.json` and a `deno` entry field also added to your `package.json`.\n\nConsumers of your package who use `make-deno-edition` on their own package, will now be able to use your package's deno edition to further their own deno compatibility.\n\nYou can also instruct consumers of your package to directly use your deno edition, by informing them of its presence in your `README.md` file. You can use [`projectz`](https://github.com/bevry/projectz) to automatically insert this information for them, or you can use the following template:\n\n \n\n\n\n\n\n\n\n\n#### Sponsors\n\n- [Andrew Nesbitt](https://nesbitt.io) — Software engineer and researcher\n- [Balsa](https://balsa.com) — We're Balsa, and we're building tools for builders.\n- [Codecov](https://codecov.io) — Empower developers with tools to improve code quality and testing.\n- [Poonacha Medappa](https://poonachamedappa.com)\n- [Rob Morris](https://github.com/Rob-Morris)\n- [Sentry](https://sentry.io) — Real-time crash reporting for your web apps, mobile apps, and games.\n- [Syntax](https://syntax.fm) — Syntax Podcast\n\n#### Donors\n\n- [Andrew Nesbitt](https://nesbitt.io)\n- [Armen Mkrtchian](https://mogoni.dev)\n- [Balsa](https://balsa.com)\n- [Chad](https://opencollective.com/chad8)\n- [Codecov](https://codecov.io)\n- [dr.dimitru](https://veliovgroup.com)\n- [Elliott Ditman](https://elliottditman.com)\n- [entroniq](https://gitlab.com/entroniq)\n- [GitHub](https://github.com/about)\n- [Hunter Beast](https://cryptoquick.com)\n- [Jean-Luc Geering](https://github.com/jlgeering)\n- [Michael Duane Mooring](https://mdm.cc)\n- [Michael Harry Scepaniak](https://michaelscepaniak.com)\n- [Mohammed Shah](https://github.com/smashah)\n- [Mr. Henry](https://mrhenry.be)\n- [Nermal](https://arjunaditya.vercel.app)\n- [Pleo](https://pleo.io)\n- [Poonacha Medappa](https://poonachamedappa.com)\n- [Rob Morris](https://github.com/Rob-Morris)\n- [Robert de Forest](https://github.com/rdeforest)\n- [Sentry](https://sentry.io)\n- [ServieJS](https://github.com/serviejs)\n- [Skunk Team](https://skunk.team)\n- [Syntax](https://syntax.fm)\n- [WriterJohnBuck](https://github.com/WriterJohnBuck)\n\n\n\n\n\n## License\n\nUnless stated otherwise all works are:\n\n- Copyright © [Benjamin Lupton](https://balupton.com)\n\nand licensed under:\n\n- [Artistic License 2.0](http://spdx.org/licenses/Artistic-2.0.html)\n\n\n","readmeFilename":"README.md","gitHead":"9ecfb4926ad07e9f2a701cb8457ec3b2809d3e7d","_nodeVersion":"20.10.0","_npmVersion":"10.2.3","dist":{"integrity":"sha512-KqH9cwePJDMjPmsaHAXesTtKwqZi9pdsVgo8DhIkXmZamMTYVLjJD6uNDqDI9rXPn8HRy1PG5x2TWuvbIf182w==","shasum":"6cf40b5b028df0fb2122c8b252c152566c02ad15","tarball":"https://registry.npmjs.org/make-deno-edition/-/make-deno-edition-2.3.0-next.1703871236.9ecfb4926ad07e9f2a701cb8457ec3b2809d3e7d.tgz","fileCount":24,"unpackedSize":108006,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICz4SubzxHhx/rNWhzRBYplUAa180SURIVgcuVaExCn2AiArNMbtFKzaQMRz+9TSGp2j8GfOuqfDk5AJ36cjTIQjNA=="}]},"_npmUser":{"name":"bevryme","email":"us@bevry.me"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/make-deno-edition_2.3.0-next.1703871236.9ecfb4926ad07e9f2a701cb8457ec3b2809d3e7d_1703871286853_0.8046487737000716"},"_hasShrinkwrap":false}},"time":{"created":"2020-06-10T04:35:16.300Z","0.1.0-next.1591763714.5d9046016e6453793c3b55701cbe7e8e09bc935b":"2020-06-10T04:35:16.460Z","modified":"2023-12-29T17:34:47.184Z","0.1.0-next.1591768661.e07f9a2c4e0a7cfe6fc06b0a4975aeb8ed432d7a":"2020-06-10T05:57:43.063Z","0.1.0-next.1591768699.02af05056c1432abd67db513ec36a57325cd24b0":"2020-06-10T05:58:20.541Z","0.1.0":"2020-06-10T05:59:00.012Z","0.1.1-next.1591768933.14a9478256117f828c40bab1abb8f1d974c65e22":"2020-06-10T06:02:14.659Z","0.1.1":"2020-06-10T06:02:28.482Z","0.1.2-next.1591769738.c3923afe76b72d2deaca01c3ed11942e3be09907":"2020-06-10T06:15:39.286Z","0.1.2":"2020-06-10T06:15:50.427Z","0.1.2-next.1591771040.2e9e2d069cad4f2b4b4474e844284b0a93aa78f0":"2020-06-10T06:37:22.064Z","0.1.2-next.1591772714.3735c8b511eae5482e273e901ed267b45d5910f7":"2020-06-10T07:05:15.588Z","0.1.2-next.1591773631.c78a1fb276f5c0a071c76292f8b105fbe29b756e":"2020-06-10T07:20:33.227Z","0.1.2-next.1591776134.05c122c6aa3fae72f360cc7ed72b504fa3cc7c4c":"2020-06-10T08:02:15.598Z","0.1.2-next.1591776398.bb87d13056e7f7a5ed8250400a48e07e9c726034":"2020-06-10T08:06:40.229Z","0.1.2-next.1591777457.28a5d9be482513aecc6ff5112b81b68a4de387b0":"2020-06-10T08:24:21.020Z","0.1.2-next.1591777792.88b7d06436eef3283e2292b4b8cff34ef38b7096":"2020-06-10T08:29:53.952Z","0.1.2-next.1591780704.782f43b3bfe367099fe6e5aba2f7834ed7093bd7":"2020-06-10T09:18:26.080Z","0.2.0-next.1591781692.613886e803034dc88b844b6275d755581e2dd0f4":"2020-06-10T09:34:54.389Z","0.2.0":"2020-06-10T09:35:00.336Z","0.2.1-next.1591782452.8ea203f189c45c15811e840338cce0b92da541df":"2020-06-10T09:47:34.176Z","0.2.1":"2020-06-10T09:47:45.914Z","0.2.1-next.1591783149.fb9e5a7f3598bb7221b981932cf5046769572646":"2020-06-10T09:59:10.679Z","0.2.2-next.1591784029.bca9a2437b04681001d8eac28f38e9c836c0dfae":"2020-06-10T10:13:50.787Z","0.2.2":"2020-06-10T10:13:57.933Z","0.2.2-next.1591784799.e99ce476dab8e42ec3ccc82a9f3bb6b3777af53c":"2020-06-10T10:26:41.372Z","0.2.2-next.1591785235.ca7faa3afb8ad02065a73d34506575e43b65ef24":"2020-06-10T10:33:56.717Z","0.2.2-next.1591786549.ca5b3eb8afc1f6b9aec0cab886faaba35728792c":"2020-06-10T10:55:51.202Z","0.2.2-next.1591786573.de317065e0f114c79af385efb955f2c68b45af88":"2020-06-10T10:56:15.041Z","0.2.2-next.1591786626.f3b129534d468ee3ec705407c1ed814d784769ac":"2020-06-10T10:57:07.937Z","0.2.2-next.1591786678.9303696dc77ce47fbbcc4340f302ef2434c6fd13":"2020-06-10T10:57:59.815Z","0.2.2-next.1591787154.73f6e782f6e2da542b06fc859945865041254489":"2020-06-10T11:05:56.353Z","0.2.2-next.1591788574.26fd89fa778cf9f61222f7b1f9eb8daa00328956":"2020-06-10T11:29:35.904Z","0.2.2-next.1591797913.843774d7ffce557e942485d68f2cfd53f8a078b8":"2020-06-10T14:05:14.760Z","0.3.0-next.1591798837.36e2648b411bf79f5e312fed5b9c9892c884b7e3":"2020-06-10T14:20:39.391Z","0.3.0":"2020-06-10T14:20:47.680Z","0.4.0-next.1592596058.e581edc8f07a0c65d497bbd0a962f302946cd26c":"2020-06-19T19:47:39.978Z","0.4.0":"2020-06-19T19:47:43.018Z","0.4.1-next.1592596307.1b18f3334de9d7d4526b27ef6ecfc1bfa7c06820":"2020-06-19T19:51:49.175Z","0.4.1":"2020-06-19T19:52:04.323Z","0.4.2-next.1592596401.86aaf7ad277889ea39d2bc2c91547dd069d7736e":"2020-06-19T19:53:23.615Z","0.4.2":"2020-06-19T19:53:38.896Z","0.5.1":"2020-06-19T20:10:50.701Z","0.5.1-next.1592597450.19f0dcf11f4ec98334cc05a629bdc1642f0b285c":"2020-06-19T20:11:11.467Z","0.6.0-next.1592598062.cb17d2b97c2c47a7fb25524e112f6354bcd42d33":"2020-06-19T20:21:04.211Z","0.6.0":"2020-06-19T20:21:08.351Z","0.6.1-next.1592599251.f23b666a8e9cdf07f8e139525931f121d2ebe969":"2020-06-19T20:40:52.757Z","0.6.1":"2020-06-19T20:41:02.774Z","0.7.0-next.1592606758.8b74ba681234d57cba6c77c663f720e41face75f":"2020-06-19T22:45:59.559Z","0.7.0":"2020-06-19T22:46:23.843Z","0.7.0-next.1592611911.e6ddd382e68d0ac3faebf1a19f892b80e5d3008f":"2020-06-20T00:11:53.263Z","0.8.0-next.1592613105.54e21793f099409e69e0923b45a9e7af0d54389e":"2020-06-20T00:31:46.510Z","0.8.0":"2020-06-20T00:31:55.477Z","0.8.1-next.1592615612.63555d353898c7931c148d0d4091fd4ad88872c4":"2020-06-20T01:13:33.794Z","0.8.1":"2020-06-20T01:13:42.847Z","0.8.1-next.1592617734.cd428e2af86e1d5e57bef8bd4a3d15cd3604d478":"2020-06-20T01:48:55.463Z","0.8.1-next.1592626969.9841650c59607880cd9cd2770da594568815d6cb":"2020-06-20T04:22:50.752Z","0.9.0-next.1592628745.b5a825f71cd4f09125bb04f55d0d46d256fc3591":"2020-06-20T04:52:27.209Z","0.9.0":"2020-06-20T04:52:31.208Z","0.9.1-next.1592684928.d7383900c037314557caf0986d011ef6fbbf314a":"2020-06-20T20:28:50.192Z","0.9.1":"2020-06-20T20:29:09.895Z","0.10.0-next.1592761348.537a3e0d45bee69f016a2f7e78efba8216ada164":"2020-06-21T17:42:29.939Z","0.10.0":"2020-06-21T17:42:40.185Z","0.11.0-next.1593019496.73997fbaecb71341b230f2d6dd017cda293b2c4f":"2020-06-24T17:24:57.735Z","0.11.0":"2020-06-24T17:25:10.911Z","0.11.0-next.1593019810.536558f3c711ed453e36e37fd588b86f558cd314":"2020-06-24T17:30:11.446Z","0.11.0-next.1593022025.38132cbf44c4a8671f8ebd084699e6815e76d9c8":"2020-06-24T18:07:06.792Z","0.11.0-next.1593022731.4007477998f5de593e52dd0aa0c7ce1337b0a915":"2020-06-24T18:18:52.857Z","0.11.1-next.1593023852.e09600f2ec4fe05380f0e1090325407cc5224585":"2020-06-24T18:37:34.578Z","0.11.1":"2020-06-24T18:38:16.777Z","0.12.0":"2020-06-24T23:04:33.491Z","0.13.0":"2020-06-24T23:54:10.551Z","0.13.0-next.1593042892.a4ce04b999dae63334bf1eeb59fae70fec51485d":"2020-06-24T23:54:54.214Z","0.13.0-next.1593052023.2d969013d2b924b762f64d624a2962cc9166b9b1":"2020-06-25T02:27:05.285Z","0.14.0":"2020-06-25T03:53:16.807Z","0.14.0-next.1593057187.971555b61dd11eeff2d670b4fb0d8ec5f9a31c65":"2020-06-25T03:54:25.277Z","0.14.0-next.1595337353.40e2f34e9f0ef30c8ce53375e13cfd7467f4bbf1":"2020-07-21T13:15:55.569Z","0.14.0-next.1595381393.14a05906a707c420dbfef5908f76aef702c6569f":"2020-07-22T01:29:54.478Z","0.14.0-next.1595381421.78d81cc97e109d5f44a6db5b924d705381e07b14":"2020-07-22T01:30:23.293Z","0.14.0-next.1595381916.431416ebe6a0caa455f2ac9551b76f8cf5fc4ca7":"2020-07-22T01:38:37.766Z","0.15.0-next.1595383280.f4a7638842dacefbb0f9ddefc5ba4ae056264c18":"2020-07-22T02:01:21.985Z","0.15.0":"2020-07-22T02:01:42.347Z","0.15.0-next.1595543405.07ad14dfcf99a67a09cb7a65ff80f6b698f363fb":"2020-07-23T22:30:06.752Z","0.15.0-next.1595543510.406e9ab96087ea427604faea0e236172e467add1":"2020-07-23T22:31:52.372Z","0.15.0-next.1595543534.2440e609391f4a78f18c661dbb8b2280df38e1c2":"2020-07-23T22:32:16.119Z","0.15.0-next.1595543877.b86fcb9f1082c36aacdc16db23bfdfef5da2d5e7":"2020-07-23T22:37:59.088Z","0.15.0-next.1595543904.19c08022d07342877caa61e28559fead3275ae95":"2020-07-23T22:38:25.664Z","0.15.0-next.1595544405.67f1642dda9043a09fbe6dfa0b17bf846584879f":"2020-07-23T22:46:46.890Z","0.15.0-next.1595544424.60195b2821deb5abbf983022dd2219d09b117569":"2020-07-23T22:47:06.067Z","0.15.0-next.1596504687.441de68344d58735361699d98c31f00fa69728ed":"2020-08-04T01:31:29.824Z","0.15.0-next.1596504986.f7838ee42abe62c3fcb8debfb61139e03fdcf76b":"2020-08-04T01:36:28.556Z","0.15.0-next.1597642926.ff88fba7e6ff073b7d9bdd748973b76b642a9676":"2020-08-17T05:42:07.898Z","1.0.0-next.1597643355.1939e1a422a66f9e338ebd39fa210598e258fcb2":"2020-08-17T05:49:16.847Z","1.0.0":"2020-08-17T05:49:27.060Z","1.0.0-next.1597643634.28a9bd533fc6e5c05d9ea16d16b929c75b112366":"2020-08-17T05:53:56.311Z","1.0.0-next.1597658596.b10e8e299573d109ecd6d96c6d345385c145be3c":"2020-08-17T10:03:18.432Z","1.0.1-next.1597707212.6f8d7eddcfa659b54222c38cf5aff297a9be22ec":"2020-08-17T23:33:34.518Z","1.0.1":"2020-08-17T23:33:47.685Z","1.0.2-next.1597707332.b839d2f904275a5b76585556b9c5d44b3f182f7c":"2020-08-17T23:35:34.299Z","1.0.2":"2020-08-17T23:35:44.701Z","1.0.3-next.1597775363.101863cd8e040451e26c1542979faafd021e13a0":"2020-08-18T18:29:25.081Z","1.0.3":"2020-08-18T18:29:29.992Z","1.0.3-next.1597776061.d3b234c7af1de0f8be4a783779c3b86f9631c907":"2020-08-18T18:41:02.904Z","1.1.0-next.1599107309.13e6245c58b879c60fcb21033d0d783a7fa728a7":"2020-09-03T04:28:31.363Z","1.1.0":"2020-09-03T04:28:47.830Z","1.1.1-next.1599201156.eb7229966ff4f7ec22df43465b22e904be0694c2":"2020-09-04T06:32:38.646Z","1.1.1":"2020-09-04T06:32:51.864Z","1.2.0-next.1603916556.050074421120cc0deaa07f34de8effbc4a496624":"2020-10-28T20:22:37.556Z","1.2.0":"2020-10-28T20:22:45.980Z","1.2.0-next.1603916642.257ccdadbb4456f19159176b6b7ca187840ebfa6":"2020-10-28T20:24:04.578Z","1.2.0-next.1604236622.7c588be18d4fae04e981190fa47b698a600164ca":"2020-11-01T13:17:03.636Z","1.2.0-next.1604237149.5a0612a057690cc4184ed095c7b5d2ea465d17e4":"2020-11-01T13:25:51.102Z","1.2.0-next.1604237725.60ef5bcfb35c66628007f062cd982151f56f727e":"2020-11-01T13:35:27.407Z","1.2.0-next.1604238446.cb487894694c6a16e6f1bde27c85dfff1f2b6c03":"2020-11-01T13:47:27.701Z","1.2.0-next.1604238645.63afafa14feea343812867de08683d0475f99985":"2020-11-01T13:50:47.147Z","1.3.0":"2021-06-14T06:55:43.645Z","1.3.0-next.1623653803.41fe7f9f85f49263e22074da19c184c2bbb90397":"2021-06-14T06:56:45.283Z","2.0.0":"2023-11-24T12:02:12.257Z","2.0.0-next.1700827330.c63909eb3f7216f6381862ac26b5c9d57ce9ec82":"2023-11-24T12:03:15.695Z","2.0.1-next.1701773766.bfd1ce07694efb78f43b52b3c043f0feee3d4706":"2023-12-05T10:56:08.422Z","2.0.1":"2023-12-05T11:00:56.482Z","2.1.0-next.1701820492.1cb148750ff5151a6d46b75f48225428bddc9920":"2023-12-05T23:54:53.869Z","2.1.0":"2023-12-05T23:55:16.115Z","2.2.0-next.1703696930.8bf83148bea3b04dde36798626c1774962bc0d40":"2023-12-27T17:08:52.465Z","2.2.0":"2023-12-27T17:08:54.980Z","2.3.0":"2023-12-29T17:33:53.686Z","2.3.0-next.1703871236.9ecfb4926ad07e9f2a701cb8457ec3b2809d3e7d":"2023-12-29T17:34:47.008Z"},"maintainers":[{"name":"bevryme","email":"us@bevry.me"}],"description":"Automatically makes package.json projects (such as npm packages and node.js modules) compatible with Deno.","homepage":"https://github.com/bevry/make-deno-edition","keywords":["denoify","edition","editions","es2022","node","npm","transpile","typed","types","typescript","unpkg"],"repository":{"type":"git","url":"git+https://github.com/bevry/make-deno-edition.git"},"contributors":[{"name":"Benjamin Lupton","email":"b@lupton.cc","url":"https://balupton.com"}],"author":{"name":"Benjamin Lupton","email":"b@lupton.cc","url":"https://balupton.com"},"bugs":{"url":"https://github.com/bevry/make-deno-edition/issues"},"license":"Artistic-2.0","readme":"","readmeFilename":""}