bug: Not supported for use in TypeScript, the default export init is not of function type.

[rxliuli]

ref: https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBMAdsGAaOBvOBjArvAXzgDMoIQ4ByAK2AFMAjAQwFoB3JgZxEoG4AofgHohcQLOJgQMjAWP+B-eUAUroFklQKP6gbwzAuEqBpzUBoyvyYcUCZDAAUASgH88JgESBaOUByyoC65QIg2gR0VAMSqBftUBm1oEkbQEB6gP6pgPo2gOSagKYW1ugwULh05sKiANpUDi4enpTolH7+WVQhEZRwALr8QA

[fengkx]

Typescript resolve to main filed of package.json by default which is the entrypoint for Node.js. It doesn't have(require) a init function.
https://www.typescriptlang.org/play/?target=99#code/JYWwDg9gTgLgBMAdsGAaOBvAxgVxgXzgDMoIQ4ByAK2AFMAjAQwFoB3RgZxAHowBrAObdWDbjQaMA+lA6T2XCgG4AUI3YoEyGAAoAlMuVA

import from the web entrypoint will fix the problem. I don't know how to make typecript use browser field for now.

[rxliuli]

Typescript resolve to main filed of package.json by default which is the entrypoint for Node.js. It doesn't have(require) a init function. https://www.typescriptlang.org/play/?target=99#code/JYWwDg9gTgLgBMAdsGAaOBvAxgVxgXzgDMoIQ4ByAK2AFMAjAQwFoB3RgZxAHowBrAObdWDbjQaMA+lA6T2XCgG4AUI3YoEyGAAoAlMuVA

import from the web entrypoint will fix the problem. I don't know how to make typecript use browser field for now.

The npm package you published lacks the types field in its package.json. Link to the package.json

I'm not sure about your build process, but you need to declare the exports field in the package.json and use different entry points and type definitions for different environments. Refer to the Node.js documentation

Here is an example:

// package.json
{
  "exports": {
    ".": {
      "require": {
        "types": "pkg/nodejs/jieba_rs_wasm.d.ts",
        "default": "pkg/nodejs/jieba_rs_wasm.js"
      },
      "node": {
        "types": "pkg/nodejs/jieba_rs_wasm.d.ts",
        "default": "pkg/nodejs/jieba_rs_wasm.js"
      },
      "browser": {
        "types": "pkg/web/jieba_rs_wasm.d.ts",
        "default": "pkg/web/jieba_rs_wasm.js"
      }
    }
  }
}