blocks|key|2672526|text|import+has+from+'lodash/has';更好，因为lodash将它的所有函数都保存在一个文件中，所以与其导入100k的整个“lodash”库，不如只导入lodash的has函数，可能是2k。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2672527|entityMap^0|0|T|2K|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

<code>import has from 'lodash/has';</code> is better because lodash holds all it's functions in a single file, so rather than import the whole 'lodash' library at 100k, it's better to just import lodash's <code>has</code> function which is maybe 2k.

blocks|key|2884093|text|如果你正在使用babel，你应该看看babel-plugin-lodash，它会为你精心挑选你正在使用的lodash的各个部分，更少的麻烦和更小的捆绑包。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2884094|它有几个limitations|2884095|supported|2884096|Chain+|unordered-list-item|2884097|
|2884098|您必须使用ES2015导入来加载Lodash|2884099|2884100|Babel+<6&+Node.js+<4+aren+supported|2884101|2884102|Chain+sequences不支持。请参阅此alternatives.|2884103|2884104|Modularized+blog+post+method+packages+aren+supported|2884105|2884106|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/lodash/babel-plugin-lodash|1|https://github.com/lodash/babel-plugin-lodash#limitations|2|https://medium.com/making-internets/why-using-chain-is-a-mistake-9bc1f80d51ba|3|https://www.npmjs.com/browse/keyword/lodash-modularized^0|I|J|0|0|4|B|1|0|0|0|0|0|0|0|0|0|0|C|9|2|M|F|3|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|D|3|E|5|6|7|1G|8|@]|9|@$A|1H|B|1I|1|1J]]|C|$]]|$1|F|3|G|5|6|7|1K|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1L|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1M|8|@]|9|@]|C|$]]|$1|M|3|N|5|J|7|1N|8|@]|9|@]|C|$]]|$1|O|3|L|5|6|7|1O|8|@]|9|@]|C|$]]|$1|P|3|Q|5|J|7|1P|8|@]|9|@]|C|$]]|$1|R|3|L|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1R|8|@]|9|@]|C|$]]|$1|U|3|L|5|6|7|1S|8|@]|9|@]|C|$]]|$1|V|3|W|5|J|7|1T|8|@]|9|@$A|1U|B|1V|1|1W]|$A|1X|B|1Y|1|1Z]]|C|$]]|$1|X|3|-4|5|6|7|20|8|@]|9|@]|C|$]]|$1|Y|3|-4|5|6|7|21|8|@]|9|@]|C|$]]]|Z|$10|$5|11|12|13|C|$14|15]]|16|$5|11|12|13|C|$14|17]]|18|$5|11|12|13|C|$14|19]]|1A|$5|11|12|13|C|$14|1B]]]]

If you are using babel, you should check out <a href="https://github.com/lodash/babel-plugin-lodash" rel="nofollow noreferrer">babel-plugin-lodash</a>, it will cherry-pick the parts of lodash you are using for you, less hassle and a smaller bundle.

It has a few <a href="https://github.com/lodash/babel-plugin-lodash#limitations" rel="nofollow noreferrer">limitations</a>:

<ul>
<li>You must use ES2015 imports to load Lodash</li>
<li>Babel &lt; 6 &amp; Node.js &lt; 4 aren’t supported</li>
<li>Chain sequences aren’t supported. See this <a href="https://medium.com/making-internets/why-using-chain-is-a-mistake-9bc1f80d51ba" rel="nofollow noreferrer">blog post</a> for alternatives.</li>
<li>Modularized <a href="https://www.npmjs.com/browse/keyword/lodash-modularized" rel="nofollow noreferrer">method packages</a> aren’t supported</li>
</ul>

blocks|key|2884138|text|如果你使用的是webpack+4，下面的代码是树形摇摆的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2884139|import+{+has+}+from+'lodash-es';|code-block|syntax|javascript|2884140|要注意的几点；|2884141|2884142|CommonJS模块是不可树摇动的，因此您绝对应该使用lodash-es，这是导出为ES模块的Lodash库，而不是lodash+(CommonJS).|ordered-list-item|2884143|lodash-es's+package.json+contains+"sideEffects":+false，它通知webpack+4软件包中的所有文件都是无副作用的(请参见https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free).|2884144|This信息对于树摇动至关重要，因为模块捆绑包不会树摇动文件，即使其导出的成员不在任何地方使用。|2884145|2884146|编辑|BOLD|2884147|因此，import+{+has+}+from+'lodash-es';也可以与As+of+version+1.9.0,+Parcel+also+supports+"sideEffects":+false一起摇动树木。它还支持树摇动CommonJS模块，尽管根据my+experiment的说法，ES模块的树摇动可能比CommonJS更有效。|2884148|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/lodash-es|1|https://www.npmjs.com/package/lodash|2|https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free|3|https://medium.com/@devongovett/parcel-v1-9-0-tree-shaking-2x-faster-watcher-and-more-87f2e1a70f79|4|https://github.com/kimamula/tree-shaking-demo^0|7|9|0|0|0|0|R|9|1M|6|R|9|0|1M|6|1|0|0|9|Y|K|2F|25|2|0|0|0|0|2|0|3|W|29|K|13|1Q|3|3M|D|4|0^^$0|@$1|2|3|4|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1J|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1K|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1M|8|@$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]]|D|@$9|1R|A|1S|1|1T]|$9|1U|A|1V|1|1W]]|E|$]]|$1|Q|3|R|5|P|7|1X|8|@$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]]|D|@$9|22|A|23|1|24]]|E|$]]|$1|S|3|T|5|P|7|25|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|26|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|27|8|@$9|28|A|29|B|X]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2A|8|@$9|2B|A|2C|B|C]|$9|2D|A|2E|B|C]]|D|@$9|2F|A|2G|1|2H]|$9|2I|A|2J|1|2K]]|E|$]]|$1|10|3|-4|5|6|7|2L|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|17]]|18|$5|13|14|15|E|$16|19]]|1A|$5|13|14|15|E|$16|1B]]|1C|$5|13|14|15|E|$16|1D]]|1E|$5|13|14|15|E|$16|1F]]]]

If you are using <code>webpack 4</code>, the following code is tree shakable.

<pre><code>import { has } from 'lodash-es';
</code></pre>

The points to note;

<ol>
<li>CommonJS modules are not tree shakable so you should definitely use <a href="https://www.npmjs.com/package/lodash-es" rel="noreferrer"><code>lodash-es</code></a>, which is the Lodash library exported as ES Modules, rather than <a href="https://www.npmjs.com/package/lodash" rel="noreferrer"><code>lodash</code></a> (CommonJS).</li>
<li><code>lodash-es</code>'s package.json contains <code>"sideEffects": false</code>, which notifies webpack 4 that all the files inside the package are side effect free (see <a href="https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free" rel="noreferrer">https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free</a>).</li>
<li>This information is crucial for tree shaking since module bundlers do not tree shake files which possibly contain side effects even if their exported members are not used in anywhere.</li>
</ol>

Edit

<a href="https://medium.com/@devongovett/parcel-v1-9-0-tree-shaking-2x-faster-watcher-and-more-87f2e1a70f79" rel="noreferrer">As of version 1.9.0, Parcel also supports <code>"sideEffects": false</code></a>, threrefore <code>import { has } from 'lodash-es';</code> is also tree shakable with Parcel.
It also supports tree shaking CommonJS modules, though it is likely tree shaking of ES Modules is more efficient than CommonJS according to <a href="https://github.com/kimamula/tree-shaking-demo" rel="noreferrer">my experiment</a>.

blocks|key|121476|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|121477|导入花括号内的特定方法|blockquote|121478|121479|从‘lodash’导入{+map，tail，times，uniq+}；|121480|优点：|121481|121482|121483|只有一个导入行(对于相当多的functions)|unordered-list-item|121484|More可读用法：()而不是后面的javascript代码中的_.map()。|121485|121486|缺点：|121487|121488|每次我们想要使用一个新函数或停止使用另一个函数时，都需要对它进行维护和管理|121489|121490|抄袭自:亚历山大·切尔特科夫撰写的The+Correct+Way+to+Import+Lodash+Libraries+-+A+Benchmark文章。|offset|length|121491|entityMap|0|LINK|mutability|MUTABLE|url|https://www.blazemeter.com/blog/the-correct-way-to-import-lodash-libraries-a-benchmark^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|H|1K|0|0^^$0|@$1|2|3|-4|4|5|6|18|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|19|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]|$1|E|3|F|4|5|6|1B|7|@]|8|@]|9|$]]|$1|G|3|H|4|5|6|1C|7|@]|8|@]|9|$]]|$1|I|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|1E|7|@]|8|@]|9|$]]|$1|K|3|L|4|M|6|1F|7|@]|8|@]|9|$]]|$1|N|3|O|4|M|6|1G|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|1H|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|1I|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|1J|7|@]|8|@]|9|$]]|$1|T|3|U|4|M|6|1K|7|@]|8|@]|9|$]]|$1|V|3|-4|4|5|6|1L|7|@]|8|@]|9|$]]|$1|W|3|X|4|5|6|1M|7|@]|8|@$Y|1N|Z|1O|1|1P]]|9|$]]|$1|10|3|-4|4|5|6|1Q|7|@]|8|@]|9|$]]]|11|$12|$4|13|14|15|9|$16|17]]]]

<blockquote>
Import specific methods inside of curly brackets
<pre><code>import { map, tail, times, uniq } from 'lodash';
</code></pre>
Pros:
<ul>
<li>Only one import line(for a decent amount of functions)</li>
<li>More readable usage: map() instead of _.map() later in the javascript code.</li>
</ul>
Cons:
<ul>
<li>Every time we want to use a new function or stop using another - it needs to be maintained and managed</li>
</ul>
</blockquote>
Copied from:<a href="https://www.blazemeter.com/blog/the-correct-way-to-import-lodash-libraries-a-benchmark" rel="noreferrer">The Correct Way to Import Lodash Libraries - A Benchmark</a> article written by Alexander Chertkov.

blocks|key|118587|text|您可以将它们导入为|type|unstyled|depth|inlineStyleRanges|entityRanges|data|118588|import+{concat,+filter,+orderBy}+from+'lodash';|code-block|syntax|javascript|118589|或as|118590|import+concat+from+'lodash/concat';
import+orderBy+from+'lodash/orderBy';
import+filter+from+'lodash/filter';|118591|第二个比第一个优化了很多，因为它只加载所需的模块|118592|然后像这样使用|118593|pendingArray:+concat(
++++++++++++++++++++orderBy(
++++++++++++++++++++++++filter(payload,+obj+=>+obj.flag),
++++++++++++++++++++++++['flag'],
++++++++++++++++++++++++['desc'],
++++++++++++++++++++),
++++++++++++++++++++filter(payload,+obj+=>+!obj.flag),|118594|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

You can import them as 

<pre><code>import {concat, filter, orderBy} from 'lodash';
</code></pre>

or as

<pre><code>import concat from 'lodash/concat';
import orderBy from 'lodash/orderBy';
import filter from 'lodash/filter';
</code></pre>

the second one is much optimized than the first because it only loads the needed modules

then use like this

<pre><code>pendingArray: concat(
 orderBy(
 filter(payload, obj =&gt; obj.flag),
 ['flag'],
 ['desc'],
 ),
 filter(payload, obj =&gt; !obj.flag),
</code></pre>

blocks|key|121576|text|我只是将它们放在自己的文件中，并将其导出为node和webpack：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|121577|//+lodash-cherries.js
module.exports+=+{
++defaults:+require('lodash/defaults'),
++isNil:+require('lodash/isNil'),
++isObject:+require('lodash/isObject'),
++isArray:+require('lodash/isArray'),
++isFunction:+require('lodash/isFunction'),
++isInteger:+require('lodash/isInteger'),
++isBoolean:+require('lodash/isBoolean'),
++keys:+require('lodash/keys'),
++set:+require('lodash/set'),
++get:+require('lodash/get'),
}|code-block|syntax|javascript|121578|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I just put them in their own file and export it for node and webpack:
<pre class="lang-js prettyprint-override"><code>// lodash-cherries.js
module.exports = {
 defaults: require('lodash/defaults'),
 isNil: require('lodash/isNil'),
 isObject: require('lodash/isObject'),
 isArray: require('lodash/isArray'),
 isFunction: require('lodash/isFunction'),
 isInteger: require('lodash/isInteger'),
 isBoolean: require('lodash/isBoolean'),
 keys: require('lodash/keys'),
 set: require('lodash/set'),
 get: require('lodash/get'),
}
</code></pre>

blocks|key|2884225|text|我认为这个answer可以很容易地在任何项目中使用，并且以更少的努力带来最好的结果。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2884226|对于Typescript用户，请按如下方式使用：|2884227|//+lodash.utils.ts
export+{+default+as+get+}+from+'lodash/get';
export+{+default+as+isEmpty+}+from+'lodash/isEmpty';
export+{+default+as+isNil+}+from+'lodash/isNil';
...|code-block|syntax|javascript|2884228|和导入lodash的使用方法相同：|2884229|//some-code.ts
import+{+get+}+from+'./path/to/lodash.utils'

export+static+function+getSomething(thing:+any):+any+{
++++return+get(thing,+'someSubField',+'someDefaultValue')
}|2884230|或者如果您希望保留_以避免冲突(例如，来自rxjs的map+vs+lodash)|style|CODE|2884231|//some-other-code.ts
import+*+as+_+from+'./path/to/lodash.utils'

export+static+function+getSomething(thing:+any):+any+{
++++return+_.get(thing,+'someSubField',+'someDefaultValue')
}|2884232|更新:似乎正确的导出方式是：|2884233|export+*+as+get+from+'lodash/get';
export+*+as+isEmpty+from+'lodash/isEmpty';
export+*+as+isNil+from+'lodash/isNil';
...|2884234|但是与@types/lodash有一个奇怪的冲突，我删除了这个类型的包，因为我会得到这个错误：|2884235|导出模块'"/../project/node_modules/@types/lodash/cloneDeep"‘使用’|2884236|+=‘，不能与'export+*’一起使用。.ts(2498)|blockquote|2884237|2884238|2884239|更新：|2884240|在深入研究之后，我将tsconfig.json+feature+esModuleInterop转换为true，它允许我执行以下操作：|2884241|import+get+from+'lodash/get';
import+isEmpty+from+'lodash/isEmpty';
import+isNil+from+'lodash/isNil';
...

export+{+get,+isEmpty,+isNil,+...+};|2884242|请注意，这会影响已定义为import+*+as+lib+from+'lib'的项目中的所有导入。按照文档进行操作，以确保它适合您。|2884243|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/66084580|1|https://www.typescriptlang.org/tsconfig#esModuleInterop^0|5|6|0|0|0|0|0|0|9|1|L|4|Q|3|X|6|0|0|0|0|3|D|0|0|0|0|0|0|A|D|1E|4|W|F|1|0|0|C|Q|0^^$0|@$1|2|3|4|5|6|7|1P|8|@]|9|@$A|1Q|B|1R|1|1S]]|C|$]]|$1|D|3|E|5|6|7|1T|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1U|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1V|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1W|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|1X|8|@$A|1Y|B|1Z|Q|R]|$A|20|B|21|Q|R]|$A|22|B|23|Q|R]|$A|24|B|25|Q|R]]|9|@]|C|$]]|$1|S|3|T|5|H|7|26|8|@]|9|@]|C|$I|J]]|$1|U|3|V|5|6|7|27|8|@]|9|@]|C|$]]|$1|W|3|X|5|H|7|28|8|@]|9|@]|C|$I|J]]|$1|Y|3|Z|5|6|7|29|8|@$A|2A|B|2B|Q|R]]|9|@]|C|$]]|$1|10|3|11|5|6|7|2C|8|@]|9|@]|C|$]]|$1|12|3|13|5|14|7|2D|8|@]|9|@]|C|$]]|$1|15|3|-4|5|6|7|2E|8|@]|9|@]|C|$]]|$1|16|3|-4|5|6|7|2F|8|@]|9|@]|C|$]]|$1|17|3|18|5|6|7|2G|8|@]|9|@]|C|$]]|$1|19|3|1A|5|6|7|2H|8|@$A|2I|B|2J|Q|R]|$A|2K|B|2L|Q|R]]|9|@$A|2M|B|2N|1|2O]]|C|$]]|$1|1B|3|1C|5|H|7|2P|8|@]|9|@]|C|$I|J]]|$1|1D|3|1E|5|6|7|2Q|8|@$A|2R|B|2S|Q|R]]|9|@]|C|$]]|$1|1F|3|-4|5|6|7|2T|8|@]|9|@]|C|$]]]|1G|$1H|$5|1I|1J|1K|C|$1L|1M]]|1N|$5|1I|1J|1K|C|$1L|1O]]]]

I think this <a href="https://stackoverflow.com/a/66084580">answer</a> can be used in any project easily and brings the best result with less effort.
For Typescript users, use as following :
<pre><code>// lodash.utils.ts
export { default as get } from 'lodash/get';
export { default as isEmpty } from 'lodash/isEmpty';
export { default as isNil } from 'lodash/isNil';
...
</code></pre>
And can be used the same way as importing lodash :
<pre><code>//some-code.ts
import { get } from './path/to/lodash.utils'

export static function getSomething(thing: any): any {
 return get(thing, 'someSubField', 'someDefaultValue')
}
</code></pre>
Or if you prefer to keep the <code>_</code> to avoid conflicts (ex. <code>map</code> from <code>rxjs</code> vs <code>lodash</code>)
<pre><code>//some-other-code.ts
import * as _ from './path/to/lodash.utils'

export static function getSomething(thing: any): any {
 return _.get(thing, 'someSubField', 'someDefaultValue')
}
</code></pre>
UPDATE :
Seems like the right way to export is :
<pre><code>export * as get from 'lodash/get';
export * as isEmpty from 'lodash/isEmpty';
export * as isNil from 'lodash/isNil';
...
</code></pre>
But there is a weird collision with <code>@types/lodash</code>, I've removed this type package because I would get this error :
<blockquote>
Module '&quot;/../project/node_modules/@types/lodash/cloneDeep&quot;' uses
'export =' and cannot be used with 'export *'.ts(2498)
</blockquote>
UPDATE :
After some digging, I've turned <code>tsconfig.json</code> feature <a href="https://www.typescriptlang.org/tsconfig#esModuleInterop" rel="nofollow noreferrer">esModuleInterop</a> to <code>true</code>, and it allows me to do the following :
<pre><code>import get from 'lodash/get';
import isEmpty from 'lodash/isEmpty';
import isNil from 'lodash/isNil';
...

export { get, isEmpty, isNil, ... };
</code></pre>
Note that this affects all your imports in your projects that has been defined as <code>import * as lib from 'lib'</code>. Follow the documentation to be sure it's suitable for you.

blocks|key|2672754|text|我认为更干净的方法就是这样导入lodash：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2672755|import+_+from+'lodash'|code-block|syntax|javascript|2672756|然后你可以使用你想要的任何东西，只需像这样使用下划线：-|2672757|_.has()|2672758|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I think the more cleaner way of importing lodash is just like this:-
<pre><code>import _ from 'lodash'
</code></pre>
then you can use what ever you want just by using this underscore just like this:-
<pre><code>_.has()
</code></pre>

blocks|key|118670|text|对于那些想继续使用_的人，只需像这样导入它们：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|118671|import+groupBy+from+'lodash/groupBy';
import+filter+from+'lodash/filter';
import+get+from+'lodash/get';

window._+=+{groupBy,+filter,+get};|code-block|syntax|javascript|118672|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For those who want to keep using _ , then just import them like this:
<pre><code>import groupBy from 'lodash/groupBy';
import filter from 'lodash/filter';
import get from 'lodash/get';

window._ = {groupBy, filter, get};
</code></pre>

blocks|key|2672860|text|import+{+cloneDeep,+groupBy+}+from+'lodash';|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2672861|我认为当您不需要使用_将数组转换为lodash对象时，这会更简单。|2672862|const+groupData+=+groupBy(expandedData,+(x)+=>+x.room.name);|2672863|entityMap^0|0|18|0|0|0|1O|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

<code>import { cloneDeep, groupBy } from 'lodash';</code>
I think this is simpler when you don't need to convert array to lodash object by using _.
<code>const groupData = groupBy(expandedData, (x) =&gt; x.room.name);</code>

I had a pull request feedback below, just wondering which way is the correct way to import lodash?

<blockquote>
 You'd better do import has from 'lodash/has'.. For the earlier version
 of lodash (v3) which by itself is pretty heavy, we should only import
 a specidic module/function rather than importing the whole lodash
 library. Not sure about the newer version (v4).
</blockquote>

<pre><code>import has from 'lodash/has';
</code></pre>

vs

<pre><code>import { has } from 'lodash';
</code></pre>

Thanks

Correct way to import lodash

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在下面得到了一个拉取请求反馈，只是想知道哪种方式是正确的导入lodash的方式？你最好从‘lodash/ has’中导入has..对于lodash的早期版本(v3)，它本身就相当繁重，我们应该只导入一个特定的模块/函数，而不是导入整个lodash库。不确定较新的版本(v4)。import has from 'loda...

问导入lodash的正确方法
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问导入lodash的正确方法EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问导入lodash的正确方法
EN