Pack npm files independent of their directory?
I have an npm project that builds multiple files to the public folder: an index.js file as well as several sub-files that I want to be conveniently accessible to the implementer.
My file structure on my machine looks like this:
|-public/
|--- index.js
|--- component1.js
|--- component2.js
My package.json is set up to include everything in the public folder in its tarball:
{
...
"main": "public/index.js",
"files": [ "public" ]
...
}
When I run the npm pack command, the resulting structure of the tarball looks like this:
|- package/
|--- public/
|------ index.js
|------ component1.js
|------ component2.js
|--- package.json
But in my package folder, I'd like everything to be on the same root level so that my implementer can just type import Component1 from "my-package-name/component1"; to get the sub-component. Is there a way to configure my package.json or npm to pack my project into the following structure?
|- package/
|--- index.js
|--- component1.js
|--- component2.js
|--- package.json
npm
asked Oct 17 '18 at 18:20
MarishaMarisha
7910
add a comment |
I have an npm project that builds multiple files to the public folder: an index.js file as well as several sub-files that I want to be conveniently accessible to the implementer.
My file structure on my machine looks like this:
|-public/
|--- index.js
|--- component1.js
|--- component2.js
My package.json is set up to include everything in the public folder in its tarball:
{
...
"main": "public/index.js",
"files": [ "public" ]
...
}
When I run the npm pack command, the resulting structure of the tarball looks like this:
|- package/
|--- public/
|------ index.js
|------ component1.js
|------ component2.js
|--- package.json
But in my package folder, I'd like everything to be on the same root level so that my implementer can just type import Component1 from "my-package-name/component1"; to get the sub-component. Is there a way to configure my package.json or npm to pack my project into the following structure?
|- package/
|--- index.js
|--- component1.js
|--- component2.js
|--- package.json
npm
asked Oct 17 '18 at 18:20
MarishaMarisha
7910
add a comment |
I have an npm project that builds multiple files to the public folder: an index.js file as well as several sub-files that I want to be conveniently accessible to the implementer.
My file structure on my machine looks like this:
|-public/
|--- index.js
|--- component1.js
|--- component2.js
My package.json is set up to include everything in the public folder in its tarball:
{
...
"main": "public/index.js",
"files": [ "public" ]
...
}
When I run the npm pack command, the resulting structure of the tarball looks like this:
|- package/
|--- public/
|------ index.js
|------ component1.js
|------ component2.js
|--- package.json
But in my package folder, I'd like everything to be on the same root level so that my implementer can just type import Component1 from "my-package-name/component1"; to get the sub-component. Is there a way to configure my package.json or npm to pack my project into the following structure?
|- package/
|--- index.js
|--- component1.js
|--- component2.js
|--- package.json
npm
asked Oct 17 '18 at 18:20
MarishaMarisha
7910
I have an npm project that builds multiple files to the public folder: an index.js file as well as several sub-files that I want to be conveniently accessible to the implementer.
My file structure on my machine looks like this:
|-public/
|--- index.js
|--- component1.js
|--- component2.js
My package.json is set up to include everything in the public folder in its tarball:
{
...
"main": "public/index.js",
"files": [ "public" ]
...
}
When I run the npm pack command, the resulting structure of the tarball looks like this:
|- package/
|--- public/
|------ index.js
|------ component1.js
|------ component2.js
|--- package.json
But in my package folder, I'd like everything to be on the same root level so that my implementer can just type import Component1 from "my-package-name/component1"; to get the sub-component. Is there a way to configure my package.json or npm to pack my project into the following structure?
|- package/
|--- index.js
|--- component1.js
|--- component2.js
|--- package.json
npm
npm
asked Oct 17 '18 at 18:20
MarishaMarisha
7910
asked Oct 17 '18 at 18:20
MarishaMarisha
7910
asked Oct 17 '18 at 18:20
MarishaMarisha
7910
asked Oct 17 '18 at 18:20
MarishaMarisha
7910
asked Oct 17 '18 at 18:20
MarishaMarisha
7910
7910
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I ended up accomplishing this by moving my package.json file to my /public folder, then packing and publishing from that folder instead, then moving package.jsonback. If you can automate this process with a script, it is not too much of an inconvenience.
answered Nov 27 '18 at 20:54
MarishaMarisha
7910
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%2f52861304%2fpack-npm-files-independent-of-their-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
I ended up accomplishing this by moving my package.json file to my /public folder, then packing and publishing from that folder instead, then moving package.jsonback. If you can automate this process with a script, it is not too much of an inconvenience.
answered Nov 27 '18 at 20:54
MarishaMarisha
7910
add a comment |
I ended up accomplishing this by moving my package.json file to my /public folder, then packing and publishing from that folder instead, then moving package.jsonback. If you can automate this process with a script, it is not too much of an inconvenience.
answered Nov 27 '18 at 20:54
MarishaMarisha
7910
add a comment |
I ended up accomplishing this by moving my package.json file to my /public folder, then packing and publishing from that folder instead, then moving package.jsonback. If you can automate this process with a script, it is not too much of an inconvenience.
answered Nov 27 '18 at 20:54
MarishaMarisha
7910
I ended up accomplishing this by moving my package.json file to my /public folder, then packing and publishing from that folder instead, then moving package.jsonback. If you can automate this process with a script, it is not too much of an inconvenience.
answered Nov 27 '18 at 20:54
MarishaMarisha
7910
answered Nov 27 '18 at 20:54
MarishaMarisha
7910
answered Nov 27 '18 at 20:54
MarishaMarisha
7910
answered Nov 27 '18 at 20:54
MarishaMarisha
7910
7910
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%2f52861304%2fpack-npm-files-independent-of-their-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
