Import-cost discrepency in modularised npm package
I'm importing a part of the Async library in my project, but I basically only need to use the eachlimit function.
From previous experience with the library, I remember that there are (like Lodash) modularized packages like async.eachlimit. however, they seem to be deprecated since the official package seems to support modular imports of the package:
However, when actually using this import method, I see a huge difference in file size between the async.eachlimit and async/eachlimit import methods (provided by import-costs)
import * as eachLimit from 'async.eachlimit'; // 2K (gzipped: 725)
import eachLimit from 'async/eachlimit'; // 10.7K (gzipped: 3.8K)
These are supposed to be the same library, albeit different versions, but this size difference seems immense for what should probably not be this big of a library.
So I'm not sure what's going wrong. Is this just import-cost being inaccurate, or could that specific package really have quintupled?
javascript npm webpack
asked Nov 20 '18 at 14:25
MarcoMarco
418214
add a comment |
I'm importing a part of the Async library in my project, but I basically only need to use the eachlimit function.
From previous experience with the library, I remember that there are (like Lodash) modularized packages like async.eachlimit. however, they seem to be deprecated since the official package seems to support modular imports of the package:
However, when actually using this import method, I see a huge difference in file size between the async.eachlimit and async/eachlimit import methods (provided by import-costs)
import * as eachLimit from 'async.eachlimit'; // 2K (gzipped: 725)
import eachLimit from 'async/eachlimit'; // 10.7K (gzipped: 3.8K)
These are supposed to be the same library, albeit different versions, but this size difference seems immense for what should probably not be this big of a library.
So I'm not sure what's going wrong. Is this just import-cost being inaccurate, or could that specific package really have quintupled?
javascript npm webpack
asked Nov 20 '18 at 14:25
MarcoMarco
418214
Side note:import * as eachLimit from 'async.eachLimit'imports the package's namespace object. I suspect you meant to import its default import:import eachLimit from 'async.eachLimit';.
– T.J. Crowder
Nov 20 '18 at 14:29
I replaced the picture with code now. As for the side note: that's something that's on Typescript, they require that for some packages ¯_(ツ)_/¯
– Marco
Nov 20 '18 at 15:12
I think you might want to double-check that. Again, it imports the namespace object, not the default import, creating the namespace object if it doesn't already exist. I don't buy that TypeScript requires that.
– T.J. Crowder
Nov 20 '18 at 15:15
add a comment |
I'm importing a part of the Async library in my project, but I basically only need to use the eachlimit function.
From previous experience with the library, I remember that there are (like Lodash) modularized packages like async.eachlimit. however, they seem to be deprecated since the official package seems to support modular imports of the package:
However, when actually using this import method, I see a huge difference in file size between the async.eachlimit and async/eachlimit import methods (provided by import-costs)
import * as eachLimit from 'async.eachlimit'; // 2K (gzipped: 725)
import eachLimit from 'async/eachlimit'; // 10.7K (gzipped: 3.8K)
These are supposed to be the same library, albeit different versions, but this size difference seems immense for what should probably not be this big of a library.
So I'm not sure what's going wrong. Is this just import-cost being inaccurate, or could that specific package really have quintupled?
javascript npm webpack
asked Nov 20 '18 at 14:25
MarcoMarco
418214
I'm importing a part of the Async library in my project, but I basically only need to use the eachlimit function.
From previous experience with the library, I remember that there are (like Lodash) modularized packages like async.eachlimit. however, they seem to be deprecated since the official package seems to support modular imports of the package:
However, when actually using this import method, I see a huge difference in file size between the async.eachlimit and async/eachlimit import methods (provided by import-costs)
import * as eachLimit from 'async.eachlimit'; // 2K (gzipped: 725)
import eachLimit from 'async/eachlimit'; // 10.7K (gzipped: 3.8K)
These are supposed to be the same library, albeit different versions, but this size difference seems immense for what should probably not be this big of a library.
So I'm not sure what's going wrong. Is this just import-cost being inaccurate, or could that specific package really have quintupled?
javascript npm webpack
javascript npm webpack
asked Nov 20 '18 at 14:25
MarcoMarco
418214
asked Nov 20 '18 at 14:25
MarcoMarco
418214
edited Nov 20 '18 at 15:10
Marco
asked Nov 20 '18 at 14:25
MarcoMarco
418214
asked Nov 20 '18 at 14:25
MarcoMarco
418214
asked Nov 20 '18 at 14:25
MarcoMarco
418214
418214
Side note:import * as eachLimit from 'async.eachLimit'imports the package's namespace object. I suspect you meant to import its default import:import eachLimit from 'async.eachLimit';.
– T.J. Crowder
Nov 20 '18 at 14:29
I replaced the picture with code now. As for the side note: that's something that's on Typescript, they require that for some packages ¯_(ツ)_/¯
– Marco
Nov 20 '18 at 15:12
I think you might want to double-check that. Again, it imports the namespace object, not the default import, creating the namespace object if it doesn't already exist. I don't buy that TypeScript requires that.
– T.J. Crowder
Nov 20 '18 at 15:15
add a comment |
Side note:import * as eachLimit from 'async.eachLimit'imports the package's namespace object. I suspect you meant to import its default import:import eachLimit from 'async.eachLimit';.
– T.J. Crowder
Nov 20 '18 at 14:29
I replaced the picture with code now. As for the side note: that's something that's on Typescript, they require that for some packages ¯_(ツ)_/¯
– Marco
Nov 20 '18 at 15:12
I think you might want to double-check that. Again, it imports the namespace object, not the default import, creating the namespace object if it doesn't already exist. I don't buy that TypeScript requires that.
– T.J. Crowder
Nov 20 '18 at 15:15
Side note:
import * as eachLimit from 'async.eachLimit' imports the package's namespace object. I suspect you meant to import its default import: import eachLimit from 'async.eachLimit';.– T.J. Crowder
Nov 20 '18 at 14:29
Side note:
import * as eachLimit from 'async.eachLimit' imports the package's namespace object. I suspect you meant to import its default import: import eachLimit from 'async.eachLimit';.– T.J. Crowder
Nov 20 '18 at 14:29
I replaced the picture with code now. As for the side note: that's something that's on Typescript, they require that for some packages ¯_(ツ)_/¯
– Marco
Nov 20 '18 at 15:12
I replaced the picture with code now. As for the side note: that's something that's on Typescript, they require that for some packages ¯_(ツ)_/¯
– Marco
Nov 20 '18 at 15:12
I think you might want to double-check that. Again, it imports the namespace object, not the default import, creating the namespace object if it doesn't already exist. I don't buy that TypeScript requires that.
– T.J. Crowder
Nov 20 '18 at 15:15
I think you might want to double-check that. Again, it imports the namespace object, not the default import, creating the namespace object if it doesn't already exist. I don't buy that TypeScript requires that.
– T.J. Crowder
Nov 20 '18 at 15:15
add a comment |
0
active
oldest
votes
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%2f53395141%2fimport-cost-discrepency-in-modularised-npm-package%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53395141%2fimport-cost-discrepency-in-modularised-npm-package%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
Side note:
import * as eachLimit from 'async.eachLimit'imports the package's namespace object. I suspect you meant to import its default import:import eachLimit from 'async.eachLimit';.– T.J. Crowder
Nov 20 '18 at 14:29
I replaced the picture with code now. As for the side note: that's something that's on Typescript, they require that for some packages ¯_(ツ)_/¯
– Marco
Nov 20 '18 at 15:12
I think you might want to double-check that. Again, it imports the namespace object, not the default import, creating the namespace object if it doesn't already exist. I don't buy that TypeScript requires that.
– T.J. Crowder
Nov 20 '18 at 15:15