Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Typescript] Cannot use namespace 'cep' as a value.ts #245

Open
lucasltv opened this issue Jun 14, 2022 · 3 comments
Open

[Typescript] Cannot use namespace 'cep' as a value.ts #245

lucasltv opened this issue Jun 14, 2022 · 3 comments

Comments

@lucasltv
Copy link

lucasltv commented Jun 14, 2022

Someone else has the same problem when using with Typescript?

Steps to reproduce:

import cep, { CEP } from 'cep-promise';

....

const data = await cep(str, {});

Version: 4.1.2

I think that is a conflict definition for library.

@lucasltv
Copy link
Author

Just a workaround, adding the ts ignore next line comment:

// @ts-ignore: Unreachable code error
const data: CEP = await cep(str, {});

@victorfernandesraton
Copy link

@lucasltv you should try cep-any project

https://github.com/victorfernandesraton/cep-any

@henriquemachad0
Copy link

Someone else has the same problem when using with Typescript?

Steps to reproduce:

import cep, { CEP } from 'cep-promise';

....

const data = await cep(str, {});

Version: 4.1.2

I think that is a conflict definition for library.

Someone else has the same problem when using with Typescript?

Steps to reproduce:

import cep, { CEP } from 'cep-promise';

....

const data = await cep(str, {});

Version: 4.1.2

I think that is a conflict definition for library.

Someone else has the same problem when using with Typescript?

Steps to reproduce:

import cep, { CEP } from 'cep-promise';

....

const data = await cep(str, {});

Version: 4.1.2

I think that is a conflict definition for library.

Same problem here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants