Skip to content
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

Closed
mindreframer opened this issue Jun 9, 2024 · 8 comments
Closed

Bug: usage of private packages #8

mindreframer opened this issue Jun 9, 2024 · 8 comments

Comments

@mindreframer
Copy link

When I try to run pnpm install on a freshly cloned repo, I get the following output:

pnpm install
Scope: all 8 workspace projects
Lockfile is up to date, resolution step is skipped
Packages: +1054
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 ERR_PNPM_FETCH_401  GET https://npm.pkg.github.com/download/@journeyapps-platform/cli-logger/2.14.8/8e699780eb6240fcd755feaf2d6fc70063334ea3: Unauthorized - 401

No authorization header was set for the request.

No authorization settings were found in the configs.
Try to log in to the registry by running "pnpm login"
or add the auth tokens manually to the ~/.npmrc file.
Progress: resolved 1054, reused 486, downloaded 1, added 1

There seems to be more of private journeyapps-platform packages:

cat pnpm-lock.yaml |grep @journeyapps-platform/
      '@journeyapps-platform/deploy-cli':
      '@journeyapps-platform/deploy-config':
      '@journeyapps-platform/deploy-transformers':
      '@journeyapps-platform/formatter-cli':
      '@journeyapps-platform/lerno':
      '@journeyapps-platform/micro-cli':
      '@journeyapps-platform/micro-dev':
      '@journeyapps-platform/micro':
      '@journeyapps-platform/micro':
      '@journeyapps-platform/micro-migrate':
      '@journeyapps-platform/micro-dev':
      '@journeyapps-platform/micro':
      '@journeyapps-platform/micro-migrate':
      '@journeyapps-platform/micro-dev':

This makes local development on powersync-service impossible for all except journeyapps employees.

What would be the best way to resolve this?

Best,
Roman

@kobiebotha
Copy link
Contributor

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,
Kobie

@mindreframer
Copy link
Author

@kobiebotha Ah, sorry, missed the README part at the bottom.
Looking forward playing with this locally, when possible!

Thanks for the quick response!
Roman

@kobiebotha
Copy link
Contributor

kobiebotha commented Jun 20, 2024

@mindreframer You can keep an eye on this PR for progress updates.

@mindreframer
Copy link
Author

@mindreframer You can keep an eye on this PR for progress updates.

Awesome, I will! Thanks!

@stevensJourney
Copy link
Collaborator

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.

@Dieterbe
Copy link

Dieterbe commented Jul 4, 2024

@stevensJourney I suppose then you might want to remove the note about restricted packages and add build instructions instead?

@stevensJourney
Copy link
Collaborator

@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

@mindreframer
Copy link
Author

Thanks a lot!

Rentacookie added a commit that referenced this issue Sep 10, 2024
Implement powersync instance teardown functionality
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants