-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
@giphy/js-components throws error for throttle-debounce #182
Comments
I tried but it is not working without installing I see it is declared in you devDependencies but it seems like it is needed as a dependency instead. |
@MickL if you're using it in your code, you'll need to add I found this on stackoverflow and I don't think throttle debounce meets the below criteria of using it as a dependency. import {SomeType} from 'some-module';
export default class APackageClass {
constructor(private config: SomeType) {}
} I might be wrong though, if it is exported somehow then yeah I'll move it. I'm using the SDK in two other giphy projects and neither one have to import themselves |
I am just importing |
@MickL okay, I will move it to dependencies in the next release 👍 |
@MickL Are you still facing this problem? It seems that this issue is no longer relevant. |
This problem appears to still exist on your @giphy/js-components sandbox |
@q00u can you be more specific? I don't see any import errors here: https://codesandbox.io/s/1wq52x1w44?fontsize=14&file=/src/gif.ts Also the sandbox needs to be updated, if you're seeing the error could you try updating |
The error still exists. (Grid component works fine but in the grid.tsx Vs code was showing the error) |
I followed the sdk and sandbox to simply render a single gif: https://codesandbox.io/s/1wq52x1w44?fontsize=14&file=/src/gif.ts
But when I import renderGif:
It throws an error:
The docs do not state any dependency to
throttle-debounce
. If there are no dependencies but the types are needed in order@giphy/js-components
to work, then they should be included in the package.json of@giphy/js-components
imo.The text was updated successfully, but these errors were encountered: