Unable to install the project as an external contributor

[honzajavorek]

The repository uses private npm packages:

npm ERR! code E401
npm ERR! 401 Unauthorized - GET https://npm.pkg.github.com/download/@apify-packages/ui-components/0.86.0/6927975c9bcef7f899f41292e4b3d2b675011690 - authentication token not provided

I'm filing this as an issue, because I think it would be vital of anyone could clone this repo and contribute to it. Even if only some components of the docs could run locally, in a similar sense like this:

apify-docs/CONTRIBUTING.md

Line 83 in 82d6da5

Alternatively, you can skip the Nginx part and navigate to <http://localhost:3000/academy> or <http://localhost:3000/platform> manually instead of using links in the navbar. All relative links should work fine there. The problem with absolute links is only with shared components. The Nginx server is needed only for testing the whole setup and mapping all the different ports to a single one.

Currently, it is not possible to even successfully finish npm install of the repo.

[B4nan]

cc @jbartadev I lost track of this, do you still plan to make the package public or inline the necessary components here?

[B4nan]

@honzajavorek here are docs on how to install the package, but can't add you to the project myself

https://www.notion.so/apify/How-to-use-apify-packages-npm-registry-dfc20d3691ff4a879ef30ad2d104db75

[honzajavorek]

Thanks, but that just points to 404 😅

[honzajavorek]

Just want to stress I see two separate issues:

1. Can anyone contribute to Apify docs?
2. Can I contribute to Apify docs?

I'm sure you can give me access and I'll be able to install the thing, eventually. I filed this tracking issue mainly to discuss whether the current negative answer to the first question is a feature or bug.

[B4nan]

Yeah, it's a completely valid point, we've been struggling with this internally too. This started relatively recently when a new homepage was added which uses the shared (and private) packages. I thought the packages were already made public, but as said above, I kinda lock track of the current state and plans.

[jbartadev]

The ui-components library is published as a public package, it should be possible to install it without any authorization

https://github.com/apify-packages/shared-components/pkgs/npm/ui-components\

It's probably because there is outdated version of this package

[B4nan]

Maybe we just need to update its version, but I remember there were breaking changes. Let me have a look.

[B4nan]

Build is passing with latest version, will update in a minute.

[B4nan]

Btw @jbartadev you might want to ship v1 of those public packages, as right now, every 0.x release is considered major/breaking, so renovate won't update it automatically for us. If you would ship v1 and start distinguishing feature releases from major/breaking ones, it would help downstream to stay up to date.

[honzajavorek]

With the latest master at 8a5d1a7, I still get the following error on npm install:

npm ERR! code E401
npm ERR! 401 Unauthorized - GET https://npm.pkg.github.com/download/@apify-packages/ui-components/0.108.0/e668318fa70e3f38c6f394564dc51e12f4c350c5 - authentication token not provided