2

The following code is from the README of the Deno Chalk library. Deno/Typescript will not let it pass:

import chalk from "https://deno.land/x/chalk_deno@v4.1.1-deno/source/index.js";
// Run this in debugger and it's fine but it won't compile:
console.log(chalk.blue("Hello world!"));
console.log(eval("typeof chalk.blue"), "At runtime it's fine!");

Output:

error: TS2339 [ERROR]: Property 'blue' does not exist on type '{ (...arguments_: any[]): string; Chalk: typeof Chalk; }'. console.log(chalk.blue("Hello world!"));

Patched:

Commenting out line 3 and it runs fine! So chalk.blue is available at runtime but invisible to the compiler??

function At runtime it's fine!

Marc
  • 13,011
  • 11
  • 78
  • 98

2 Answers2

3

As we know that chalk is native to node ( as it was built primarily for nodejs) and it's porting on deno will have some errors and shortcomings as they are not mature as their parent packages and not to mention deno itself is quite new and will take time to have a robust developer friendly environment.

But in your case the chalk module can easily be replaced by the deno built in module called colors. Link :- https://deno.land/std@0.123.0/fmt/colors.ts

The link is in the format of https://deno.land/std@version/fmt/colors.ts where version should be replaced by version you want to use, at the time of writing the latest version is 0.123.0

Usage:

// importing colors library from denoland

import {red,blue,bold} from "https://deno.land/std@0.123.0/fmt/colors.ts"

console.log(red("This text will be printed in red");
console.log(blue("This text will be printed in blue");

// merging two properties

console.log(bold(red("This text will be red and bold"));

as you can see the usage is very similar to chalk module and for full API docs you can check the README provided here on denoland

code-withAshish
  • 71
  • 4
1

It's common for third-party code to have type libraries of varying quality.

The particular module that you're importing is a JavaScript file (which does not include type information). However, there is a type declaration file accompanying it at https://deno.land/x/chalk_deno@v4.1.1-deno/index.d.ts.

Deno has a mechanism for cases like these, which allows you to provide a compiler hint for the module that you're importing: the @deno-types directive. Read about it here: https://deno.land/manual@v1.14.3/typescript/types#providing-types-when-importing

You can use it like this in your case, before the import statement:

// @deno-types="https://deno.land/x/chalk_deno@v4.1.1-deno/index.d.ts"
import chalk from "https://deno.land/x/chalk_deno@v4.1.1-deno/source/index.js";

A bit of context: At present, you'll find quite a few modules at deno.land/x which are simply copied directly from npm packages. Lots of these don't include types, and many still are not even in proper ESM format (using bare specifiers without import maps, etc.), making them completely incompatible with Deno. This variable quality is just the nature of using third-party software (no matter which ecosystem), and unfortunate for you as a consumer, because it increases your work of auditing your dependencies.

jsejcksn
  • 27,667
  • 4
  • 38
  • 62