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.

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

Module replacement feature #19

Closed
szkiba opened this issue Oct 8, 2023 · 1 comment
Closed

Module replacement feature #19

szkiba opened this issue Oct 8, 2023 · 1 comment
Labels
feature Feature Request

Comments

@szkiba
Copy link
Collaborator

szkiba commented Oct 8, 2023

Feature Description

In some cases, it can be useful to use another path instead of the module path registered in the extension registry. For example, using a forked repository, or using a local file-system path in the case of a native builder. These use cases would be solved by the module replacement feature.

Suggested Solution

New --replace flag:

--replace name=path replaces the module path, where name is the dependency/module name and path is a remote module path (version should be appended with @) or an absolute local file-system path (a path starting with . can also be used, which will be resolved to an absolute path). It implies the use of the native builder (--builder native) and clean flag (--clean)

@szkiba szkiba added the feature Feature Request label Oct 8, 2023
@szkiba
Copy link
Collaborator Author

szkiba commented Oct 10, 2023

The v0.4.0 release includes this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature Request
Projects
None yet
Development

No branches or pull requests

1 participant