You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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, wherename
is the dependency/module name andpath
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 thenative
builder (--builder native
) and clean flag (--clean
)The text was updated successfully, but these errors were encountered: