Charlike Mike Reagent

icon indicating a website link https://calldata.space

icon company Open Source & @nodejs since 2014 icon location Bravo military timezone icon location Software Engineer • Minimalist • INTJ-T • Doing @badgen, @helapkg, @conventional-commits & @node-formidable, @regexhq and @datetime.

Results 826 comments of Charlike Mike Reagent

Parse is filtering out Dates

Sweeeet! :) You can release it as plugin now, so we can add it to the readme :tada:

Parse is filtering out Dates

@TooTallNate, btw, it seems that it would override existing regular argument with same name? For example ```js const foo = (foo, { bar, abc = 123, foo = 5 })...

Parse is filtering out Dates

Oh yea, really, mislooked the things.

Parse is filtering out Dates

Hey @TooTallNate, do you mind adding a PR with it? Next release (#138) can just include it. So we can add it to bullets of default supported features :P

Parse is filtering out Dates

Sweet, looks even more good.

module and main entry points are not exporting the same API

Strange... it's `export default`.. I will check it later today

module and main entry points are not exporting the same API

Those are the configs for Rollup.. https://github.com/tunnckoCoreLabs/hela-config-tunnckocore/tree/v0.5.19/config It creates ... Minute later: I think I got what's the problem. `parse-function` does not have `pkg.legacy` and `pkg.unpkg` fields which are needed...

module and main entry points are not exporting the same API

In anyway... i will release #138 in day or two, for sure. So everything will be simplified in terms of usage and dev workflow / building.

module and main entry points are not exporting the same API

Can you give me what's the difference between them? What's exported by both?

module and main entry points are not exporting the same API

Consistency is good thing, yea. But it's totally normal to expect require-ing esm to return an object with default key property. That's why it's in the module field. Because bundlers...