rikukissa/typehole

Issues

• Allow typeholes in other files

  #10 opened 4 years ago by andrew-ironforge
  5

• ESM support

  #23 opened 2 years ago by d7sd6u
  1

• Thank you!

  #22 opened 2 years ago by VldMrgnn
  1

• `ProjectPath` error on windows platform

  #21 opened 3 years ago by wang1212
  0

• Allow choosing `type` instead of `interface`

  #19 opened 3 years ago by akafaneh
  3

• Why is export 'default output xxx'? I'm expecting an interface

  #17 opened 4 years ago by thomas-void0
  4

• Running NodeJS server in Docker Container

  #13 opened 4 years ago by ahmad2smile
  5

• Typehole not picking up nulls

  #14 opened 4 years ago by andrew-ironforge
  4

• Respect prettier format

  #16 opened 4 years ago by rwu823
  2

• typehole not working with angular?

  #15 opened 4 years ago by bertutron
  3

• Could this run without VS code?

  #5 opened 4 years ago by beaussan
  2

• typehole.tNaN

  #7 opened 4 years ago by rikukissa
  4

• Allow typeholes on functions

  #11 opened 4 years ago by andrew-ironforge
  1

• Typehole import persists even after calling "Remove all typeholes from all files"

  #9 opened 4 years ago by sevenfields-matt
  1

• VS Code Warning Underline won't go away if initial run fails

  #8 opened 4 years ago by sevenfields-matt
  1

• Add a license

  #6 opened 4 years ago by rikukissa
  0

• Ask the user where to install runtime when there are multiple package.json files in the project

  #2 opened 4 years ago by rikukissa
  1

• Use type assertion when no variable binding is around

  #4 opened 4 years ago by rikukissa
  0

• 2 typeholes in the same file can cause duplicate interface names

  #3 opened 4 years ago by rikukissa
  0

• Force interface names to PascalCase

  #1 opened 4 years ago by rikukissa
  1