Results 26 comments of Ron Birk

I guess there is no way to have my module in my library using a different instance so I tried doing this instead in the lib module: for (let lang...

I ended up doing a variation of that where the library has to merge its language resources into the main app's ones. I wish the library could have used its...

I would love to have this. What is needed to get this reviewed? It's been six months.

We cannot use distinctUntilChanged() as the issue is the first value that comes in. I think there a good chance we don't need the test for touched in the Clarity...

"--git-remote xxx" solved it for me. With it I was able to use a different remote name than origin.

Our lerna.json file: ``` { "lerna": "2.9.1", "npmClient": "yarn", "useWorkspaces": true, "version": "independent", "conventionalCommits": true, "changelogPreset": "@cmbu/gerrit", "registry": "https://build-artifactory.xxx.com/artifactory/api/npm/npm/", "rejectCycles": true, "command": { "publish": { "registry": "https://build-artifactory.xxx.com/artifactory/api/npm/npm-local", "message": "chore(release): release...

Add silly loglevel: ``` lerna info git Pushing tags... lerna sill gitPush origin lerna lerna WARN gitPush Warning: Identity file /home/jenkins/.ssh/bellevue-ci not accessible: No such file or directory. lerna WARN...

Downgraded to lerna 3.22 and everything works again. I don't understand how publishing to npm could be affected by this? I guess lerna code goes directly to artifactory and not...

I tried adding --no-verify-access and no difference. Still 403 with lerna 5. Worked with lerna 3. `yarn run lerna publish --yes --no-verify-access `

I am assuming we should stay with lerna 3 as v5 is not working properly?