I am using vercel to deploy and I am getting this error, Jem and lib are both local packages that are installed like so "jem": "file:../lib", and "lib": "file:../lib",. this is my vercel settings. This is working on my local deployment with the vercel cli but not working when I use the Github production. any help would be great. Not I am using svelte.
You need to install types for libraries you install. Try this:
npm install #types/jem
Related
I have my helm plugin code pushed to a Azure devops repo and I want other developers to install the helm plugin with the following command
helm plugin install https://dev.azure.com/xyz/_git/my-helm-plugin
I am getting a Cannot detect VCS error when I do this. Any ideas how to overcome this?
Helm version 3.6.2
From your command, you are using the Azure Repo source.
The cause of this issue is that the repo URL is not correct.
You can try the following format
helm plugin install https://dev.azure.com/organization/project/_git/my-helm-plugin.git
In addition, you may encounter authentication issue. You can also add credential in the url.
For example:
helm plugin install https://PersonalAccesstoken#dev.azure.com/organization/project/_git/my-helm-plugin.git
I have a really simple repo in GitHub (/Hooks/), currently containing just 1 file, a simple Hooks.ts typescript file. On my local machine, in my Workspace, I've created a project folder and I can yarn add normal repositories like yarn add fuse.js but I wanted to yarn add my private repo yarn add Hooks using this format yarn add git+ssh//git#github.com:OrganisationName/Hooks.git but I just get Error: couldn't find the binary git'. I have permissions to the Hooks repo because I can push/pull from it. I'm on OSX Mojave (10.14.16) and installed Yarn via brew. My yarn version (yarn -v) is 1.22.10. This is the latest brew will install after running brew upgrade yarn.
This error "couldn't find the binary git" is related with not having installed git where the installation is made, Are you running these. commands inside a container?
you might as well be installing openssh, is necessary too.
for example in an alpine container
apk add --no-cache git openssh
yarn install
If, just in case, you don't want to access to the repo trough SSH, you can access trough https+deploy-token, heres a gitlab example:
git+https://<token-name>:<token>#gitlab.com/Username/Repository#<branch|tag>
I am having trouble running a build on travis. On our local jenkins machine everything is fine. The travis build fails with the following state
Unable to find version '4.8.0.770-beta' of package 'Lucene.Net'.
The solution folder contains a nuget.config file that specifies multiple nuget feeds. My guess is that something is going wrong there. I could use some help.
The project is on GitHub at https://github.com/RHEAGROUP/docupanel
New to Nexus and I am trying to get it working with github for authentication/authorization.
I do have Nexus running and can successfully npm login, install, and publish following their docs using the default admin user. Now, I am trying to secure my nexus npm repos with github auth.
Any help would be appreciated.
If you still have the problem, there is a plugin for nexus to do exactly that: https://github.com/larscheid-schmitzhermes/nexus3-github-oauth-plugin
Disclaimer: I am one of the authors of the plugin.
I’m trying to set up an operation where the only internet access to external repos is via artifactory server. I have followed the bower information on this web page http://www.jfrog.com/confluence/display/RTF/Bower+Repositories
I can successfully do the npm installs of bower-art-resolver as described (utilizing npm remote repository for npmjs in artifactory), but then trying to do the example bower install of bootstrap it fails because bower is attempting to find git://github.com/twbs/bootstrap.git and I don't have an access to github.com due to firewalls.
How do I make the full bower workflow work then if having the bower registry remote repository is not suffient to make the setup work? Is there some way that the artifactory VCS functions come into play? How would I make bower utilize that instead of trying to reach github.com?
This firewall scenario seems like a common use case for a repository server, so I'm sure I'm missing something.
Make sure you are doing the following:
(1) Create a remote repository in Artifactory proxying the Bower registry. Notice that Artifactory will need to access both the Bower registry and Github.
(2) Configure Bower to use the Artifactory repository you created in the previous step as the Bower registry. This should be done in the .bowerrc file, for example:
{
"registry": "http://localhost:8081/artifactory/api/bower/bower-repo"
}
(3) Use bower-art instead of bower when installing packages, for example:
bower-art install bootstrap