Could not find a declaration file for module 'MIMEText'. about mimetext HOT 14 CLOSED

@andreid42tech type declaration is scoped with declare module 'mimetext' so ideally, there shouldn't be any conflict but I'll check this out and maybe will just publish dist and types as you have suggested. I need a few days for this, thanks for bringing this up.

besides, i would recommend to check if there is any package you have installed called @types/mimetext. remove it if exists.

from mimetext.

closing this issue as all the type recognition issues has been resolved.

from mimetext.

hi @andreid42tech that was probably because of the naming issue in the type declaration file, just fixed it. could you update and confirm that the issue resolved?

from mimetext.

hi @andreid42tech that was probably because of the naming issue in the type declaration file, just fixed it. could you update and confirm that the issue resolved?

Hey, it didn't help.

from mimetext.

@andreid42tech could you share your setup so I can simulate your environment and test it? Share repository if possible, or your ide, package.json and other config files.

from mimetext.

@andreid42tech could you share your setup so I can simulate your environment and test it? Share repository if possible, or your ide, package.json and other config files.

That would be difficult, something to mention is that we are using the mono-repos with multiple tsconfigs and I would guess that there's something messy happening because mimetext comes with its full source code and its tsconfig inside node_modules, maybe we should ship only the dist and TS typings?

from mimetext.

@andreid42tech type declaration is scoped with declare module 'mimetext' so ideally, there shouldn't be any conflict but I'll check this out and maybe will just publish dist and types as you have suggested. I need a few days for this, thanks for bringing this up.

besides, i would recommend to check if there is any package you have installed called @types/mimetext. remove it if exists.

Thanks!

from mimetext.

hi @andreid42tech update to the latest version please, is the problem still continue?

from mimetext.

Hey @muratgozel, yes, I think it is due to this library being sourced fully and not bundled/compiled, could that be true?

from mimetext.

I'm getting the same error when switching typescript config moduleResolution to node16

This is most likely related to the mess that is es modules, either this repo needs to support esm or just stick to using commonjs modules

See similar issue microsoft/TypeScript#51406

from mimetext.

I am facing the same issue with "mimetext": "^3.0.16",

Here is the sample tsconfig.

{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "bundler",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
  "exclude": ["node_modules"]
}

from mimetext.

Here is the error

Looks like it is trying to resolve es module one and cannot use the type

from mimetext.

Just sent a PR which fixes this for me: #50

It's a bit clunky and doesn't handle CJS but should at least get things working for ES users.

from mimetext.

@andreid42tech i have updated type generations, give it another go if possible, please, it should all be fixed now.

from mimetext.