I have some scoped public packages on npm registry as using scopes seems to be a good practice in general. Of course I have the same username on npm registry and GitHub and both registries require that the scope I can publish to is my username - which all makes sense. I have published a private package to GPR call it `@activescott/my-private-package`. I can install that package successfully using the `.npmrc` as follows registry=https://npm.pkg.github.com/activescott
always-auth=true and the following install command: $ npm install @firstname.lastname@example.org The issue comes when I try to install a public package with this command: npm add @activescott/eslint-config I get the following error: npm ERR! code E404
npm ERR! 404 Not Found - GET https://npm.pkg.github.com/activescott/@activescott%2feslint-config - npm package "eslint-config" does not exist under owner "activescott"
... How can I pull some packages from the same scope that are private on GPR and public on npm registry?
... View more
I am running into the common Your site is having problems building: The symbolic link /blue.css targets a file which does not exist within your site's repository. I know this is a common issue and have read the linked documentation carefully. The issue is that the symlink it is referring to in the repo at https://github.com/activescott/blogs.pingpoet.com/blob/master/docs/blue.css and the linked target is indeed in the repository. In fact, if you hit that link from the github pages published site at http://blogs.pingpoet.com/blue.css, it even works! Am I missing something?
... View more