-
Notifications
You must be signed in to change notification settings - Fork 16
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
Bug: usage of private packages #8
Comments
Hi Roman, This is mentioned in the README, albeit at the very bottom.... We're currently working on removing these dependencies and should be done this week. Best, |
@kobiebotha Ah, sorry, missed the README part at the bottom. Thanks for the quick response! |
@mindreframer You can keep an eye on this PR for progress updates. |
Awesome, I will! Thanks! |
Hi @mindreframer , the PR mentioned above has now been merged. It is now possible to install all packages, build and run the service locally. I'll close this for now. |
@stevensJourney I suppose then you might want to remove the note about restricted packages and add build instructions instead? |
Indeed! Thanks for mentioning, this will be fixed in #32 |
Thanks a lot! |
Implement powersync instance teardown functionality
When I try to run
pnpm install
on a freshly cloned repo, I get the following output:There seems to be more of private
journeyapps-platform
packages:This makes local development on powersync-service impossible for all except journeyapps employees.
What would be the best way to resolve this?
Best,
Roman
The text was updated successfully, but these errors were encountered: