Closed jcamden closed 3 years ago
Hi! Looks like this issue is related to #74 and #77, looks like I broke package.json by this #74 change. I will check all this stuff as soon as i will have free minute :(
Hi @YuriGor, just wanted to bump this. The workaround mentioned above (unplugging deepdash and removing "type" : "module"
from package.json) still works, so not a big problem; but it seemed good to give updated confirmation of the issue. Thanks again for deepdash!
Hi, thank you for patience, I had no time. Will try to look on this week.
Hi @jcamden thank you for motivation, otherwise I would probably never made myself to care about this :) Could you please check v5.3.7? both packages 'deepdash' and 'deepdash-es' was updated to support recent nodejs "exports" package feature, so if you have nodejs>12 - it should help. Webpack should also support this feature, so please try.
Hi @YuriGori, the vs-code Typescript server compiles imports from 5.3.7 without any need to unplug and modify the package.json.
However, Webpack throws an error. Here it is for your standalone method (which is cool):
ERROR in ...superTopSecretUI/SpaceAlienPhone.tsx 23:19-52
Module not found: Error: Package path ./standalone is not exported from package /secureComputer/topSecretProjects/secret-intergalactic-social-media-platform/.yarn/cache/deepdash-es-npm-5.3.7-d50725dacf-97ced85397.zip/node_modules/deepdash-es/ (see exports field in /secureComputer/topSecretProjects/secret-intergalactic-social-media-platform/.yarn/cache/deepdash-es-npm-5.3.7-d50725dacf-97ced85397.zip/node_modules/deepdash-es/package.json)
Same for cherry-pick:
ERROR in ...superTopSecretUI/SpaceAlienPhone.tsx 23:19-52
Module not found: Error: Package path ./mapValuesDeep is not exported from package /secureComputer/topSecretProjects/secret-intergalactic-social-media-platform/.yarn/cache/deepdash-es-npm-5.3.7-d50725dacf-97ced85397.zip/node_modules/deepdash-es/ (see exports field in /secureComputer/topSecretProjects/secret-intergalactic-social-media-platform/.yarn/cache/deepdash-es-npm-5.3.7-d50725dacf-97ced85397.zip/node_modules/deepdash-es/package.json)
Have a baby now, but when I get time, I will check this out further. Thanks again!
Thanks for testing, will dig deeper then!
Hi @jcamden here is a demo repo deepdash+webpack https://github.com/YuriGor/deepdash-webpack works fine for me could you please repro your issue using this as starting point?
also please try just 'deepdash', not 'deepdash-es' - 'deepdash' is now both compatible with esm and cjs
P.S. looks like in typescript, package exports property are still in progress: https://github.com/microsoft/TypeScript/issues/33079 but it still should work fine old way.
Ah, you are right, @YuriGor: the issue was that Typescript doesn't support package exports (until 4.3 in May, evidently); but the lodash mixin method works just fine without unplugging since 5.3.7. Thanks again for the very superstar support and for the excellent package. Much better than my own attempts at deep-x-lodash-method functions 👍
Greetings, YuriGor!
I'm enrolled in your Super Star Support Plan. I wanted to give you a heads up about an apparently webpack-related issue: I'm using deepdash-es for a bad idea that I had about running all of my cypress tests recursively from a single object. I'm running cypress with a questionable alpha plugin, cypress-webpack-preprocessor-v5 (because webpack 5 supports yarn 2 pnp) and using ts-loader. So in that kind of crazy context, when I attempt to use deepdash-es, I get an incredibly cryptic error from the cypress test runner:
What? Well... after fiddling around with whatever was seemingly referenced by the error, I found that unplugging deepdash-es and removing
"type" : "module"
from package.json resolves the issue. I don't quite understand, to be honest, but maybe you will. Thanks very much for the great package!