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

Property '#protocol' in type 'Collection' refers to a different member that cannot be accessed from within type 'Collection'. #146

Closed
Ankook opened this issue Jan 16, 2023 · 11 comments

Comments

@Ankook
Copy link

Ankook commented Jan 16, 2023

Trying to initialize mongoDB storage
Screenshot 2023-01-16 at 10 23 00

@Ankook
Copy link
Author

Ankook commented Jan 16, 2023

i just do a copypaste from example

@Satont
Copy link
Member

Satont commented Jan 16, 2023

@Ankook hi. I updated all packages, can you test did it work for you now?

Do not forget to recache dependency.

@Ankook
Copy link
Author

Ankook commented Jan 16, 2023

Screenshot 2023-01-16 at 19 00 48

This works for me

@Satont
Copy link
Member

Satont commented Jan 16, 2023

Screenshot 2023-01-16 at 19 00 48 This works for me

Is it deno import maps or you migrated to node instead? Because your original issue about deno.

@Ankook
Copy link
Author

Ankook commented Jan 16, 2023

Yes i migrated to node. I'll check deno dependencies now.

@Ankook
Copy link
Author

Ankook commented Jan 16, 2023

The error did not disappear after updating the packages, new dependencies lead to the same files, n
Screenshot 2023-01-16 at 21 23 14
ew versions did not appear.

@Satont
Copy link
Member

Satont commented Jan 16, 2023

The error did not disappear after updating the packages, new dependencies lead to the same files, n Screenshot 2023-01-16 at 21 23 14 ew versions did not appear.

Upgrade grammy_storages to latest version, please.

@Ankook
Copy link
Author

Ankook commented Jan 16, 2023

this error disappeared

@Ankook
Copy link
Author

Ankook commented Jan 16, 2023

Screenshot 2023-01-16 at 21 59 41

@KnorpelSenf
Copy link
Member

Does that mean that this issue is fixed so it can be closed?

@Ankook
Copy link
Author

Ankook commented Jan 16, 2023

Yes

@Ankook Ankook closed this as completed Jan 16, 2023
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

No branches or pull requests

3 participants