Publish multiple private packages to private npm registry (Sinopia) - sinopia

I have created private npm registry by installing sinopia in the machine, how can i publish multiple private packages by a single publish command instead of publishing one by one ?
I stuck in this step. Please suggest me if you have any idea.
Thanks in advance!

Related

How to create sfc package using vite for vuejs on GitHub package registry?

I want to create a monorepo of private package using vite (vueJS) in GitHub package registry.
Any npm package suggestion for it please?
Yes, there is.
You can use: npm: vue-sfc-vite or github: #afzalsabbir/vue-sfc-vite and you can take help of lerna.
To create monorepo using lerna: Follow the steps here: Github NPM Package Registry > Publish

How to use private packages in Azure Pipelines During CI/CD builds

I am using Azure CI/CD pipelines for Flutter build. In my Pubspec yaml file, I have dependencies that are private to my project and the code is hosted in same azure devops project but in different repository. During Build (i.e. Flutter Packages get) it gives me error saying Authentication failed?. I tried with PAT token where in prior to flutter build task i used git command to set that token, but it didn't solve the issue. Can anyone help me out?
I am open to being shown a better way but these are the steps I took to solve this issue a little while ago.
Assuming you are referencing the package in your pubspec.yaml using git over ssh on azure devops like:
repo_name:
git:
ref: 'tag or other identifier'
url: you#vs-ssh.visualstudio.com:v3/you/project/repo_name
Generate a new ssh key pair on your machine.
Upload the private key to the library secure files section on azure devops.
Add the install ssh key task to your azure pipelines build, using the key pair generated in the previous steps and referencing the private key uploaded to the secure files library. link
Upload the public key to your list of public keys. (This step I'm not 100% sure is necessary but I did it initially and things have worked so I haven't changed removed it)
So in my azure-pipelines.yaml the install ssh key step looks kinda like this where id_rsa is the name of the private key in my secure files.
- task: InstallSSHKey#0
inputs:
knownHostsEntry: 'vs-ssh.visualstudio.com, ...etc'
sshPublicKey: 'ssh-rsa ...etc'
sshKeySecureFile: id_rsa
A private feed is created with permissions such that only you have access.
The build agent run with user(build service account), give to this user permissions in the feed. From Feed settings->Permissions, assign your build service account owner permission.
Also verify the token is working, make sure you have selected sufficient scopes for this token to authorize for your specific tasks.
Besides try adding a variable system.debug with a value of true you’ll get more information in the failure. That might help pinpoint the problem.

Installing public npm packages from the GitHub package registry

1.I publish a public package in an organization repo.
The repo link : https://github.com/JX3BOX/jx3box-config/packages/141887
2.And I wanna install the package from another repo.
I had set the dependencies in the package.json
"dependencies": {
"#jx3box/jx3box-config": "^1.0.3",
and I created a file named .npmrc ,and set :
#jx3box:registry=https://npm.pkg.github.com
3.When I use github actions to build
There is an error occur
Running build scripts... npm install && npm run build
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="GitHub Package Registry"
It means maybe I need auth.But This is an public package.Is it should be auth too?
4.Now I had to prepend a line in the file .npmrc,just like
//npm.pkg.github.com/:_authToken=<mytoken>
But how can I set it in the actions .
or because this is a public pkg,how can I don't need any auth?
Thanks a lot!! ^_^
This is probably solved but posting anyway because this question ranks high on Google.
From the GitHub Docs:
You need an access token to publish, install, and delete packages. You can use a personal access token to authenticate with your username directly to GitHub Packages or the GitHub API.[...]
You cannot install packages (even public ones) from the GitHub npm registry without being authenticated.
More details and multiple authentication methods here:
https://docs.github.com/en/packages/guides/configuring-npm-for-use-with-github-packages#authenticating-to-github-packages
The docs should be updated.
You need an access token to publish, install, and delete packages.
This should really be changed to;
You need an access token to publish, install, and delete both private and public packages.

Prevent publishing public packages on VSTS

I created the feed to store private npm package there.
When I publish my private package from the project - some another public packages are published to this feed.
Can I somehow prevent publishing of public packages to the feed?
Is it ok to store public packages on the VSTS feed?
Daniel Mann is correct - you most likely have the npmjs upstream source. Because npm only supports a single registry, the upstream source is required to use both public and private packages in the same project. This is by design and recommended by the Azure Artifacts team. The "Source" column on your package list should show that these packages come from npmjs directly.

Gitlab - New project from Gitlab export

I'd like to create a new project on Gitlab from an export out of a private Gitlab instance. I exported the repository from the private instance and received a .tar.gz file. According to the official Gitlab.com documentation I should be able to select "from Gitlab export" when I create a new project but that menu is missing for me.
I found an issue on Gitlab but it was closed because the function was added but apparently I am still not able to use it.
Anyone ever used that function? Is there any possibility to move my repo from a private Gitlab to the public one?
Thanks in advance.
Greetings
As specified in the Gitlab documentation, importing Gitlab exports needs to be administratively enabled first. In your private instances, be sure to upgrade your Gitlab instance to at least 10.3.4 or you may open a security hole.
For the gitlab.com case, I guess it may be disabled because of this issue for now.
EDIT: in fact, now that I look at it, I do see "Gitlab export" listed as the first option.