-
Notifications
You must be signed in to change notification settings - Fork 71
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
Declaration for interface
-only file not generated in watch mode
#163
Labels
kind: bug
Something isn't working properly
topic: type-only / emit-less imports
Related to importing type-only files that will not be emitted
Comments
ezolenko
added a commit
that referenced
this issue
Jul 26, 2019
Should be fixed in 0.22.1 |
Confirmed Working , Thanks |
This was referenced Sep 18, 2019
agilgur5
added
the
topic: type-only / emit-less imports
Related to importing type-only files that will not be emitted
label
May 8, 2022
Repository owner
locked as resolved and limited conversation to collaborators
May 8, 2022
agilgur5
changed the title
Type Declaration for Interfaces is not generated in Watch mode
Declaration for Jun 5, 2022
interface
-only files not generated in watch mode
agilgur5
changed the title
Declaration for
Declaration for Jun 5, 2022
interface
-only files not generated in watch modeinterface
-only file not generated in watch mode
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind: bug
Something isn't working properly
topic: type-only / emit-less imports
Related to importing type-only files that will not be emitted
What happens and why it is wrong
Source file with only type declarations ex: Interfaces don't get declarations generated in watch mode.
The plugin is watching watching: project/packages/data-switch/DataSwitch.ts for changes
but not generating new declaration files when the file changes.
The file contains only export interface definitions.
Environment
Linux Env.
Versions
rollup.config.js
tsconfig.json
extends
plugin output with verbosity 3
The text was updated successfully, but these errors were encountered: