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

Cannot find module 'node-vibrant/node' or its corresponding type declarations when importing `node-vibrant/node' #168

Closed
Sandakan opened this issue Dec 27, 2024 · 7 comments · Fixed by #170

Comments

@Sandakan
Copy link

import { Vibrant } from 'node-vibrant/node';

This is the error i get in VSCode when I try to import 'node-vibrant/node';

Cannot find module 'node-vibrant/node' or its corresponding type declarations.
  There are types at 'PROJECT_ROOT_PATH/node_modules/node-vibrant/dist/esm/node.d.ts', but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.ts(2307)

I also found a github issue in typescript repo related to this issue.

@Sandakan
Copy link
Author

The error is now gone when I set the moduleResolution to NodeNext.
I'll keep the issue open so that you can check whether its a bug in the package.

@motabass
Copy link

motabass commented Jan 11, 2025

I face the same error when trying to import it like import { Vibrant } from 'node-vibrant/browser'; inside my angular 19 app.

TS2307: Cannot find module 'node-vibrant/browser' or its corresponding type declarations.

sadly i can't switch to another moduleResolution because angular seems not to support it.

@wendevlin
Copy link

We have the same issue for home-assistant/frontend, changing moduleResolution is no option.

@crutchcorn
Copy link
Member

image

Seems like this is an issue with our package.json bundle somehow? Lemme look into this

@crutchcorn
Copy link
Member

This should be resolved in 4.0.1. Can someone confirm for me please? :)

@wendevlin
Copy link

This should be resolved in 4.0.1. Can someone confirm for me please? :)

Thanks, looks good on my side 🎉

@motabass
Copy link

Thanks. 4.0.1 is also working for me

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

Successfully merging a pull request may close this issue.

4 participants