Attila Večerek

I'm seeing the same problem as @EdwinPhilip above. I'm running `macOS Monterey Version 12.4 (21F79)` and `devspace version 5.18.5`.

This is a great thread! I've been thinking about a fetcher that could take a set of decoders as input in form of a tagged union ([here](https://github.com/contactlab/appy/issues/322) and [here](https://github.com/contactlab/appy/pull/323)) but...

> What is the suggested behaviour in your opinion for handling incorrect url's in stub_request? @bblimke your question presumes that URLs with a trailing dot are incorrect. In fact, they...

You're right, I think we just wanted to make sure that the `.nvmrc` file is respected. Probably a better thing to do would be to run `node -v` and compare...

I see a similar error when using Node 16. Switching to Node 14 runs prettier without an issue. Unfortunately, I can't share a link to the repo because it's private.

Adding these to the setup script: ```sh npmAuthIdent: "$ARTIFACTORY_USERNAME:$ARTIFACTORY_API_KEY" # or npmAuthToken: "$ARTIFACTORY_API_KEY" ``` produces: ``` ➤ YN0041: │ @myScope/my-package@npm:1.0.8::__archiveUrl=https%3A%2F%2Fmyrepo.jfrog.io%2Fmyrepo%2Fapi%2Fnpm%2Fnpm%2F%40myScope%2Fmy-package%2F-%2F%40myScope%2Fmy-package-1.0.8.tgz: Invalid authentication (as an unknown user) ```

Yes. The script currently looks like this but it still results in the same `invalid authentication` issue: ```sh cat ~/.yarnrc.yml npmScopes: myScope: npmAuthToken: "${ARTIFACTORY_API_KEY}" npmPublishRegistry: "https://myrepo.jfrog.io/myrepo/api/npm/npm" npmRegistryServer: "https://myrepo.jfrog.io/myrepo/api/npm/npm" EOF ```

It also fails.

@merceyz bump

The workaround no longer seems to work in Node 18.6. I'm getting the following error: ``` node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node) ./script/setup-jfrog-authn: line 10: echo: write...