Closed pablolazarofever closed 2 years ago
@pablolazarofever Sorry for the late reply. Do you know what the solution is to this?
@pablolazarofever Sorry for the late reply. Do you know what the solution is to this?
Not original poster, but for now adding declare module 'astro-seo';
to my .d.ts types file fixes this. Not an npm expert, so I've no clue, but would it be possible that there are missing type declarations?
it looks like this can be solved by adding an index file at the top level and adjusting the exports
in the package.json, like how the example template does. will open a PR shortly 👍🏽
hey @jonasmerlin, can you push a new release please? this way i can remove the typedef as a workaround
P.S. @alex-grover thanks so much for the fix!
The change is now released as 0.6.0
@pablolazarofever Sorry for the late reply. Do you know what the solution is to this?
Not original poster, but for now adding
declare module 'astro-seo';
to my .d.ts types file fixes this. Not an npm expert, so I've no clue, but would it be possible that there are missing type declarations?
👀
@pablolazarofever Sorry for the late reply. Do you know what the solution is to this?
Not original poster, but for now adding
declare module 'astro-seo';
to my .d.ts types file fixes this. Not an npm expert, so I've no clue, but would it be possible that there are missing type declarations?eyes
you should no longer need to do this. in 0.6.0+, the issue should be fixed :)
@pablolazarofever Sorry for the late reply. Do you know what the solution is to this?
Not original poster, but for now adding
declare module 'astro-seo';
to my .d.ts types file fixes this. Not an npm expert, so I've no clue, but would it be possible that there are missing type declarations?eyes
you should no longer need to do this. in 0.6.0+, the issue should be fixed :)
weird... I still have to do this... ever with 0.6.0
In a fresh and empty project (with
astro-seo
version^0.5.0
installed), runningastro check
will fail if you includeastro-seo
as the documentation states.