Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow to install packages from git monorepos #1570

Closed
wclr opened this issue Oct 31, 2016 · 18 comments
Closed

Allow to install packages from git monorepos #1570

wclr opened this issue Oct 31, 2016 · 18 comments
Labels
fixed-in-modern This issue has been fixed / implemented in Yarn 2+.

Comments

@wclr
Copy link
Contributor

wclr commented Oct 31, 2016

It would be nice if yarn allowed to install packages from hosted git monorepos.

"@cycle/dom": "github:cyclejs/cyclejs/dom#123CH"

here: cyclejs/cyclejs is github monorepo path, dom is package folder inside monorepo, 123CH is commit hash (maybe it should be cyclejs/cyclejs#123CH/dom if with commit hash)
@jiripospisil
Copy link

Related https://github.com/yarnpkg/rfcs/issues/15

@sebmck
Copy link
Contributor

sebmck commented Oct 31, 2016

Closing in favor of the RFC @jiripospisil linked.

@sebmck sebmck closed this as completed Oct 31, 2016
@wclr
Copy link
Contributor Author

wclr commented Mar 12, 2017

@jiripospisil is there an RFC I can not find it, wasn't it implement yet?

@wclr wclr mentioned this issue Mar 12, 2017
Closed
@Budry
Copy link

Budry commented Mar 26, 2017

This would be very useful...Any progress or any next info about this?

@mattbrunetti
Copy link

This would add a lot of flexibility to how we use monorepos ... (+1)

@jiripospisil Any idea what happened to that issue? It's disappeared! And I thought Github issues could not be removed 🤕

@jiripospisil
Copy link

@whitecolor @mattbrunetti I'm not really sure, I cannot find it either. I think the only way an issue can be removed is either when a GitHub admin deletes it or the user gets banned / blocked.

@mattbrunetti
Copy link

@kittens Since the RFC is gone should we reopen this?

@mattwiller
Copy link

@mattbrunetti @kittens This would be useful for us as well; +1 to reopening

@wclr
Copy link
Contributor Author

wclr commented May 16, 2017

This things called yalc maybe useful who work with multiple self-authored packages in development, it simplifies workflow of package usage in the project before package is properly published, better than npm link or installing from git.

@AlexxNica
Copy link

AlexxNica commented May 24, 2017 •
edited
Loading

@whitecolor I think yall would be a better call for this problem. This seems like a good workaround for now, even though I think this should be fixed/added to the package manager itself rather than using 3rd parties to solve the problem.

@wclr
Copy link
Contributor Author

wclr commented May 24, 2017

Well, yall is a tool for mainly installing dependencies TO monorepo not FROM) anyway installing from git often doesn't work as now packages require build step, so not sure if the original issue is really actual.

@juanca
Copy link
Contributor

juanca commented May 24, 2017

This would be ideal for yarnpkg/e2e-test-repo#2

@joshcartme joshcartme mentioned this issue Nov 22, 2017
Closed
@bjankord bjankord mentioned this issue Feb 9, 2018
Closed
@numandev1
Copy link

Try https://gitpkg.now.sh/

yarn add https://gitpkg.now.sh/<user>/<repo>/<subdir>[?<branch>]

OR

"@react-native-community/cli-platform-ios":"https://gitpkg.now.sh/nomi9995/cli/packages/platform-ios?fix-ios-getProductName-regex"

@merceyz merceyz added the fixed-in-modern This issue has been fixed / implemented in Yarn 2+. label Jan 16, 2021
@MadLittleMods MadLittleMods mentioned this issue Feb 26, 2022
Merged
@Riki1312
Copy link

Riki1312 commented Mar 3, 2022

This worked well for me:

yarn add @name/package-name@https://github.com/user/repo#workspace=@name/package-name

@zbyte64
Copy link

zbyte64 commented Mar 3, 2022

The RFC linked is now missing. I don't know how this got "fixed", are we expected to use an external service like gitpkg?

@mir3z
Copy link

mir3z commented Nov 17, 2022

Any update on this?

@skyFabioCozz
Copy link

Updates?

@Pixelik
Copy link

Pixelik commented Aug 1, 2023

updates?

@squishyu squishyu mentioned this issue Sep 23, 2023
Open
@RexSkz RexSkz mentioned this issue Jan 5, 2024
Closed
1 task
JanPodmajersky added a commit to slidoapp/emoji-mart that referenced this issue May 29, 2024
@JanPodmajersky
feat: move emoji-mart package to root
8143710 
As this git repository consists of [yarn workspaces](https://yarnpkg.com/features/workspaces),
which enable to define mono repo packages within one repository, but we want
to use only one package `emoji-mart`. `slido-frontend` does not use yarn2 yet, so the workspace
can't be specified see yarnpkg/yarn#1570 (comment).

As we are of the full control of this forked repository, the fastest and easiest is to change the
folder structure to consist only of this package 🎉.

I was also considering this 3rd party subfolder generation https://github.com/EqualMa/gitpkg, but decided
not to depend on potentially security risk of 3rd party provider.
JanPodmajersky added a commit to slidoapp/emoji-mart that referenced this issue May 29, 2024
@JanPodmajersky
feat: move emoji-mart package to root
0b21608 
As this git repository consists of [yarn workspaces](https://yarnpkg.com/features/workspaces),
which enable to define mono repo packages within one repository, but we want
to use only one package `emoji-mart`. `slido-frontend` does not use yarn2 yet, so the workspace
can't be specified see yarnpkg/yarn#1570 (comment).

As we are of the full control of this forked repository, the fastest and easiest is to change the
folder structure to consist only of this package 🎉.

I was also considering this 3rd party subfolder generation https://github.com/EqualMa/gitpkg, but decided
not to depend on potentially security risk of 3rd party provider.
JanPodmajersky added a commit to slidoapp/emoji-mart that referenced this issue May 29, 2024
@JanPodmajersky
feat: move built emoji-mart package to root
d15bc9b 
As this git repository consists of [yarn workspaces](https://yarnpkg.com/features/workspaces),
which enable to define mono repo packages within one repository, but we want
to use only one package `emoji-mart`. `slido-frontend` does not use yarn2 yet, so the workspace
can't be specified see yarnpkg/yarn#1570 (comment).

As we are of the full control of this forked repository, the fastest and easiest is to change the
folder structure to consist only of this package 🎉.

I was also considering this 3rd party subfolder generation https://github.com/EqualMa/gitpkg, but decided
not to depend on potentially security risk of 3rd party provider.
JanPodmajersky added a commit to slidoapp/emoji-mart that referenced this issue May 29, 2024
@JanPodmajersky
feat: move built emoji-mart package to root
05c4135 
As this git repository consists of [yarn workspaces](https://yarnpkg.com/features/workspaces),
which enable to define mono repo packages within one repository, but we want
to use only one package `emoji-mart`. `slido-frontend` does not use yarn2 yet, so the workspace
can't be specified see yarnpkg/yarn#1570 (comment).

As we are of the full control of this forked repository, the fastest and easiest is to change the
folder structure to consist only of this package 🎉.

I was also considering this 3rd party subfolder generation https://github.com/EqualMa/gitpkg, but decided
not to depend on potentially security risk of 3rd party provider.

The dist related properties were adjusted in the root package.json from  emoji-mart package, as
this root package is used as a reference when usign this dependency.
@JanPodmajersky JanPodmajersky mentioned this issue May 29, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fixed-in-modern This issue has been fixed / implemented in Yarn 2+.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests