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

Type Extensions are not exposed/available automatically #26

Open
matei-radu opened this issue Feb 17, 2023 · 0 comments
Open

Type Extensions are not exposed/available automatically #26

matei-radu opened this issue Feb 17, 2023 · 0 comments

Comments

@matei-radu
Copy link

I'm using Hardhat with TypeScript and of course I'm using HardhatUserConfig to type my configuration. I expected the type-extensions.ts file to be picked up automatically by the TypeScript system and effectively patch that type, but that is not the case, saying that the exposed property is not defined.

To make this work, I have to import the type-extensions.ts file explicitly:

import 'hardhat-exposed/dist/type-extensions'
import { HardhatUserConfig } from 'hardhat/config'

const config: HardhatUserConfig = {
    exposed: {
      // My config
    }
}

This is not a problem and it works, however, is this the intended way to use the types?

@matei-radu matei-radu changed the title Type Extensions are not exposed/available Type Extensions are not exposed/available automatically Feb 17, 2023
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

1 participant