`babel-plugin-react-css-modules` Typescript Type Checking
up vote
0
down vote
favorite
I am using babel-plugin-react-css-modules. It add the styleName property to HTML elements. Typescript doesn't recognize this property. I am pretty sure I need to extend something but nothing I have tried has worked.
I have tried declaring an Element in a '.d.ts' file to do declaration merging but I must be doing something wrong.
interface Element {
styleName: string;
}
export const Wrapper: React.FC<IWrapperProps> = ({ children, style }) => (
<div styleName="wrapper" style={style}>
{children}
</div>
);
UPDATE:
.d.ts not working
typescript babel babel-plugin-react-css-modules
asked Nov 20 at 4:22
hipstersmoothie
73
add a comment |
up vote
0
down vote
favorite
I am using babel-plugin-react-css-modules. It add the styleName property to HTML elements. Typescript doesn't recognize this property. I am pretty sure I need to extend something but nothing I have tried has worked.
I have tried declaring an Element in a '.d.ts' file to do declaration merging but I must be doing something wrong.
interface Element {
styleName: string;
}
export const Wrapper: React.FC<IWrapperProps> = ({ children, style }) => (
<div styleName="wrapper" style={style}>
{children}
</div>
);
UPDATE:
.d.ts not working
typescript babel babel-plugin-react-css-modules
asked Nov 20 at 4:22
hipstersmoothie
73
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using babel-plugin-react-css-modules. It add the styleName property to HTML elements. Typescript doesn't recognize this property. I am pretty sure I need to extend something but nothing I have tried has worked.
I have tried declaring an Element in a '.d.ts' file to do declaration merging but I must be doing something wrong.
interface Element {
styleName: string;
}
export const Wrapper: React.FC<IWrapperProps> = ({ children, style }) => (
<div styleName="wrapper" style={style}>
{children}
</div>
);
UPDATE:
.d.ts not working
typescript babel babel-plugin-react-css-modules
asked Nov 20 at 4:22
hipstersmoothie
73
I am using babel-plugin-react-css-modules. It add the styleName property to HTML elements. Typescript doesn't recognize this property. I am pretty sure I need to extend something but nothing I have tried has worked.
I have tried declaring an Element in a '.d.ts' file to do declaration merging but I must be doing something wrong.
interface Element {
styleName: string;
}
export const Wrapper: React.FC<IWrapperProps> = ({ children, style }) => (
<div styleName="wrapper" style={style}>
{children}
</div>
);
UPDATE:
.d.ts not working
typescript babel babel-plugin-react-css-modules
typescript babel babel-plugin-react-css-modules
asked Nov 20 at 4:22
hipstersmoothie
73
asked Nov 20 at 4:22
hipstersmoothie
73
edited Nov 20 at 9:09
asked Nov 20 at 4:22
hipstersmoothie
73
asked Nov 20 at 4:22
hipstersmoothie
73
asked Nov 20 at 4:22
hipstersmoothie
73
73
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Since you're in a module (it has an export), you're working with a separate scope from the global scope - so you're just creating an interface named Element that's separate from the global declaration.
I'd place the interface in a separate file with no exports/imports (augmentations.d.ts) and add that to your tsconfig.json.
answered Nov 20 at 4:43
Daniel Rosenwasser
7,62132038
I tried that too and it didn't work :(
– hipstersmoothie
Nov 20 at 9:04
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Since you're in a module (it has an export), you're working with a separate scope from the global scope - so you're just creating an interface named Element that's separate from the global declaration.
I'd place the interface in a separate file with no exports/imports (augmentations.d.ts) and add that to your tsconfig.json.
answered Nov 20 at 4:43
Daniel Rosenwasser
7,62132038
I tried that too and it didn't work :(
– hipstersmoothie
Nov 20 at 9:04
add a comment |
up vote
0
down vote
Since you're in a module (it has an export), you're working with a separate scope from the global scope - so you're just creating an interface named Element that's separate from the global declaration.
I'd place the interface in a separate file with no exports/imports (augmentations.d.ts) and add that to your tsconfig.json.
answered Nov 20 at 4:43
Daniel Rosenwasser
7,62132038
I tried that too and it didn't work :(
– hipstersmoothie
Nov 20 at 9:04
add a comment |
up vote
0
down vote
up vote
0
down vote
Since you're in a module (it has an export), you're working with a separate scope from the global scope - so you're just creating an interface named Element that's separate from the global declaration.
I'd place the interface in a separate file with no exports/imports (augmentations.d.ts) and add that to your tsconfig.json.
answered Nov 20 at 4:43
Daniel Rosenwasser
7,62132038
Since you're in a module (it has an export), you're working with a separate scope from the global scope - so you're just creating an interface named Element that's separate from the global declaration.
I'd place the interface in a separate file with no exports/imports (augmentations.d.ts) and add that to your tsconfig.json.
answered Nov 20 at 4:43
Daniel Rosenwasser
7,62132038
answered Nov 20 at 4:43
Daniel Rosenwasser
7,62132038
answered Nov 20 at 4:43
Daniel Rosenwasser
7,62132038
answered Nov 20 at 4:43
Daniel Rosenwasser
7,62132038
7,62132038
I tried that too and it didn't work :(
– hipstersmoothie
Nov 20 at 9:04
add a comment |
I tried that too and it didn't work :(
– hipstersmoothie
Nov 20 at 9:04
I tried that too and it didn't work :(
– hipstersmoothie
Nov 20 at 9:04
I tried that too and it didn't work :(
– hipstersmoothie
Nov 20 at 9:04
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53386183%2fbabel-plugin-react-css-modules-typescript-type-checking%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
