Ansible npm module doesn't create node_modules directory
I wrote a playbook with the npm:
Ansible module, and I expected to see a node_modules
directory when I execute it. There is, however, no such directory created.
- name: install packages based on package.json
npm:
path: "{{ ansible_env.HOME }}/project_dir/"
tags: npm
Note that project_dir/package.json
exists. When I execute npm install
in this directory, it creates a node_modules
folder.
Is Ansible's npm module written correctly, based on my assumption that the behavior should be to create the node_modules directory upon running this npm module?
EDIT: the only dependencies in the package.json file are devDependencies
ansible
add a comment |
I wrote a playbook with the npm:
Ansible module, and I expected to see a node_modules
directory when I execute it. There is, however, no such directory created.
- name: install packages based on package.json
npm:
path: "{{ ansible_env.HOME }}/project_dir/"
tags: npm
Note that project_dir/package.json
exists. When I execute npm install
in this directory, it creates a node_modules
folder.
Is Ansible's npm module written correctly, based on my assumption that the behavior should be to create the node_modules directory upon running this npm module?
EDIT: the only dependencies in the package.json file are devDependencies
ansible
add a comment |
I wrote a playbook with the npm:
Ansible module, and I expected to see a node_modules
directory when I execute it. There is, however, no such directory created.
- name: install packages based on package.json
npm:
path: "{{ ansible_env.HOME }}/project_dir/"
tags: npm
Note that project_dir/package.json
exists. When I execute npm install
in this directory, it creates a node_modules
folder.
Is Ansible's npm module written correctly, based on my assumption that the behavior should be to create the node_modules directory upon running this npm module?
EDIT: the only dependencies in the package.json file are devDependencies
ansible
I wrote a playbook with the npm:
Ansible module, and I expected to see a node_modules
directory when I execute it. There is, however, no such directory created.
- name: install packages based on package.json
npm:
path: "{{ ansible_env.HOME }}/project_dir/"
tags: npm
Note that project_dir/package.json
exists. When I execute npm install
in this directory, it creates a node_modules
folder.
Is Ansible's npm module written correctly, based on my assumption that the behavior should be to create the node_modules directory upon running this npm module?
EDIT: the only dependencies in the package.json file are devDependencies
ansible
ansible
edited Jan 3 at 19:39
activedecay
asked Jan 3 at 19:32
activedecayactivedecay
3,53932139
3,53932139
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The last time this question was asked it turned out that the npm
version was too old to understand the npm list --json --long
that the module uses to decide if it needs to take any action.
Try one of two things:
- Upgrade
npm
to be a modern version - Re-run
ansible-playbook -vv
to attempt to get more information that might confirm or deny the theory
If you do experience that your npm
is too old, it would be awesome if you would file an issue with ansible about that problem
1
github.com/ansible/ansible/issues/50550
– activedecay
Jan 4 at 15:25
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%2f54028685%2fansible-npm-module-doesnt-create-node-modules-directory%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
The last time this question was asked it turned out that the npm
version was too old to understand the npm list --json --long
that the module uses to decide if it needs to take any action.
Try one of two things:
- Upgrade
npm
to be a modern version - Re-run
ansible-playbook -vv
to attempt to get more information that might confirm or deny the theory
If you do experience that your npm
is too old, it would be awesome if you would file an issue with ansible about that problem
1
github.com/ansible/ansible/issues/50550
– activedecay
Jan 4 at 15:25
add a comment |
The last time this question was asked it turned out that the npm
version was too old to understand the npm list --json --long
that the module uses to decide if it needs to take any action.
Try one of two things:
- Upgrade
npm
to be a modern version - Re-run
ansible-playbook -vv
to attempt to get more information that might confirm or deny the theory
If you do experience that your npm
is too old, it would be awesome if you would file an issue with ansible about that problem
1
github.com/ansible/ansible/issues/50550
– activedecay
Jan 4 at 15:25
add a comment |
The last time this question was asked it turned out that the npm
version was too old to understand the npm list --json --long
that the module uses to decide if it needs to take any action.
Try one of two things:
- Upgrade
npm
to be a modern version - Re-run
ansible-playbook -vv
to attempt to get more information that might confirm or deny the theory
If you do experience that your npm
is too old, it would be awesome if you would file an issue with ansible about that problem
The last time this question was asked it turned out that the npm
version was too old to understand the npm list --json --long
that the module uses to decide if it needs to take any action.
Try one of two things:
- Upgrade
npm
to be a modern version - Re-run
ansible-playbook -vv
to attempt to get more information that might confirm or deny the theory
If you do experience that your npm
is too old, it would be awesome if you would file an issue with ansible about that problem
answered Jan 3 at 23:26
Matthew L DanielMatthew L Daniel
9,50612729
9,50612729
1
github.com/ansible/ansible/issues/50550
– activedecay
Jan 4 at 15:25
add a comment |
1
github.com/ansible/ansible/issues/50550
– activedecay
Jan 4 at 15:25
1
1
github.com/ansible/ansible/issues/50550
– activedecay
Jan 4 at 15:25
github.com/ansible/ansible/issues/50550
– activedecay
Jan 4 at 15:25
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%2f54028685%2fansible-npm-module-doesnt-create-node-modules-directory%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