Mixing
How do I know what other npm projects that my current npm project is linked to?
I'm working on project1, project2 both, and project1 is linked to project2 on my local(project1 --> project2) using npm link.
How do I know that project1 is linked successfully to project2?
I have being using npm -g ls --depth=0 --link=true, but that's not exactly what I want, the command only should what symlink is created to the npm global node_module folder but not should the "linked relations between two projects".
Thanks.
linux npm devops
asked Jan 2 at 14:03
paradoxparadox
9718
add a comment |
I'm working on project1, project2 both, and project1 is linked to project2 on my local(project1 --> project2) using npm link.
How do I know that project1 is linked successfully to project2?
I have being using npm -g ls --depth=0 --link=true, but that's not exactly what I want, the command only should what symlink is created to the npm global node_module folder but not should the "linked relations between two projects".
Thanks.
linux npm devops
asked Jan 2 at 14:03
paradoxparadox
9718
add a comment |
I'm working on project1, project2 both, and project1 is linked to project2 on my local(project1 --> project2) using npm link.
How do I know that project1 is linked successfully to project2?
I have being using npm -g ls --depth=0 --link=true, but that's not exactly what I want, the command only should what symlink is created to the npm global node_module folder but not should the "linked relations between two projects".
Thanks.
linux npm devops
asked Jan 2 at 14:03
paradoxparadox
9718
I'm working on project1, project2 both, and project1 is linked to project2 on my local(project1 --> project2) using npm link.
How do I know that project1 is linked successfully to project2?
I have being using npm -g ls --depth=0 --link=true, but that's not exactly what I want, the command only should what symlink is created to the npm global node_module folder but not should the "linked relations between two projects".
Thanks.
linux npm devops
linux npm devops
asked Jan 2 at 14:03
paradoxparadox
9718
asked Jan 2 at 14:03
paradoxparadox
9718
asked Jan 2 at 14:03
paradoxparadox
9718
asked Jan 2 at 14:03
paradoxparadox
9718
asked Jan 2 at 14:03
paradoxparadox
9718
9718
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There no built-in npm command to determine which project/package(s) have been linked to another project/package via the npm link command.
However, you can install and utilize the link-status package:
Firstly, install the
link-statuspackage by running the following command:
npm install -g link-status
Then
cdto your project directory (i.e. Project2) and run the following command:
link-status
it should then log the name(s) of each project/package(s) that is symlinked. For instance:
project1
You can also utilize the
-soption. For example, if you run the following command from inside the Project2 directory:
link-status -s
it will additionally log the path to each linked package. E.g.
project1
╚═══ ../../some/path/to/node_modules/project1
answered Jan 2 at 17:24
RobCRobC
6,62392640
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54007725%2fhow-do-i-know-what-other-npm-projects-that-my-current-npm-project-is-linked-to%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There no built-in npm command to determine which project/package(s) have been linked to another project/package via the npm link command.
However, you can install and utilize the link-status package:
Firstly, install the
link-statuspackage by running the following command:
npm install -g link-status
Then
cdto your project directory (i.e. Project2) and run the following command:
link-status
it should then log the name(s) of each project/package(s) that is symlinked. For instance:
project1
You can also utilize the
-soption. For example, if you run the following command from inside the Project2 directory:
link-status -s
it will additionally log the path to each linked package. E.g.
project1
╚═══ ../../some/path/to/node_modules/project1
answered Jan 2 at 17:24
RobCRobC
6,62392640
add a comment |
There no built-in npm command to determine which project/package(s) have been linked to another project/package via the npm link command.
However, you can install and utilize the link-status package:
Firstly, install the
link-statuspackage by running the following command:
npm install -g link-status
Then
cdto your project directory (i.e. Project2) and run the following command:
link-status
it should then log the name(s) of each project/package(s) that is symlinked. For instance:
project1
You can also utilize the
-soption. For example, if you run the following command from inside the Project2 directory:
link-status -s
it will additionally log the path to each linked package. E.g.
project1
╚═══ ../../some/path/to/node_modules/project1
answered Jan 2 at 17:24
RobCRobC
6,62392640
add a comment |
There no built-in npm command to determine which project/package(s) have been linked to another project/package via the npm link command.
However, you can install and utilize the link-status package:
Firstly, install the
link-statuspackage by running the following command:
npm install -g link-status
Then
cdto your project directory (i.e. Project2) and run the following command:
link-status
it should then log the name(s) of each project/package(s) that is symlinked. For instance:
project1
You can also utilize the
-soption. For example, if you run the following command from inside the Project2 directory:
link-status -s
it will additionally log the path to each linked package. E.g.
project1
╚═══ ../../some/path/to/node_modules/project1
answered Jan 2 at 17:24
RobCRobC
6,62392640
There no built-in npm command to determine which project/package(s) have been linked to another project/package via the npm link command.
However, you can install and utilize the link-status package:
Firstly, install the
link-statuspackage by running the following command:
npm install -g link-status
Then
cdto your project directory (i.e. Project2) and run the following command:
link-status
it should then log the name(s) of each project/package(s) that is symlinked. For instance:
project1
You can also utilize the
-soption. For example, if you run the following command from inside the Project2 directory:
link-status -s
it will additionally log the path to each linked package. E.g.
project1
╚═══ ../../some/path/to/node_modules/project1
answered Jan 2 at 17:24
RobCRobC
6,62392640
answered Jan 2 at 17:24
RobCRobC
6,62392640
answered Jan 2 at 17:24
RobCRobC
6,62392640
answered Jan 2 at 17:24
RobCRobC
6,62392640
6,62392640
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54007725%2fhow-do-i-know-what-other-npm-projects-that-my-current-npm-project-is-linked-to%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
