Starting from deno@v1.28, npm compatibliity is now marked stable. I've successfully migrated some Node.js projects to deno and adding npm prefix to import {} from "npm:package-name" with import_map.json.

What in my opinion is great about Deno it how it pushes the ecosystem forward in terms of standards, so targeting node from deno with tools like dnt (a deno to npm package build tool) makes sense for a development workflow. Also, the fact Deno has built-in formatting, linting, removes the need for node_modules, package*.json, etc greatly enhances DX.

If this is still being considered, I think now might finally be an adequate time to do so (or actually continue to do so, there has been progress in other branches). Would moving the whole ecosystem e.g. packages like @feathersjs/mongodb be in order?

The following script can be used to convert dependencies in package.json to a valid import_map.json:

// main.ts - run with: `deno run -A main.ts`
const text = await Deno.readTextFile(`${Deno.cwd()}/package.json`);
const deps = JSON.parse(text).dependencies;

const importMap = {
  imports: {
    ...Object.keys(deps).reduce((acc, dep) => {
      acc[dep] = `npm:${dep}@${deps[dep].replace("^", "")}`;
      return acc;
    }, {}),
  },
};

await Deno.writeTextFile(
  `${Deno.cwd()}/importMap.json`,
  JSON.stringify(importMap, null, 2)
);

Uh oh!

Deno Support? #1964

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions