Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to use multiple version remotes like shared?

See original GitHub issue

For example.

An application contains the packages profile, home and search. The package profile provides the Profile component, and the packages home and search use the Profile component from the remote package.
The code of the Profile component was modified (some breaking changes were introduced) and the version was upgraded from 1.0 to 2.0, at which point the home package updated its code to use the latest version of 2.0. However, the code in the search package has not been updated yet, and should use the 1.0 version.

As far as I can tell, it is possible to use shared version control (e.g. using multiple versions at the same time) in managing third party dependencies such as lodash. But I haven’t found a solution in the remote package yet.

Thanks for any input.

Issue Analytics

State:
Created 3 years ago
Reactions:6
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

ScriptedAlchemycommented, Jul 3, 2021

Append the name to the remotes name property and file name . Then you can lol unique files and resolve to the right global like app1:app1v2_0

1reaction

unbugxcommented, Jan 16, 2021

@jacob-ebey thx, but unfortunately this approach is not suitable for me as I want to keep all repositories as private. The simplest solution I see is keeping different build versions of container on my own host.

Top Results From Across the Web

Working with Git remotes and pushing to multiple Git repositories

Working with two or more Git repositories? No problem! In this tutorial, you'll first learn to setup multiple Git remotes.

How do you use multiple versions of the same R package?

R's package system is set to by default to overwrite existing packages, so that you always have the latest version.

A Shared Git Repo Mirroring Multiple Remotes

Importing code from a remote repo into a local Git repo is trivial: git remote and git fetch do the hard work. However...

2.5 Git Basics - Working with Remotes

To be able to collaborate on any Git project, you need to know how to manage your remote repositories. Remote repositories are versions...

Module Federation - webpack

Shared modules are modules that are both overridable and provided as ... Could provide and consume multiple different versions when you have nested ......