The requested module '@nanoexpress/*' does not provide an export named 'default' about middlewares HOT 9 CLOSED

@dalisoft b0e7e4b solved it for body-parser. Nice!

from middlewares.

@torbjorn-kvist Please test it on both ESM and CJS mode and let me know results

from middlewares.

it seems that it can be fixed by doing this:
torbjorn-kvist@db7fd3c

Not sure how to test it without publishing an npm package, tried to do a .tgz with npm pack but was not allowed to installed. But tried to do the same changes in node_modules.

When doing these changes it works, also need to the same change in https://github.com/dalisoft/npm-packages/tree/master/packages/getdirname because schemator is using it.

It works if you import the packages as '@nanoexpress/middleware-schemator/module' but then I'm getting the same error for getdirname.

Not sure how you want to solve this, but it seems to work with the current changes on the fork.

from middlewares.

@torbjorn-kvist Can you make PR for this? If possible with tests please, i'll fix this as soon as i can, but seems it's not current month, at next month i think i can do. If you need faster result, please submit PR

from middlewares.

Can make a PR for it, but not sure how to test without another repository importing it from package.json. Will try to look into both when I get some time over.

from middlewares.

@dalisoft I was able to test body-parser on both ESM and CJS and can confirm both modes are working!

from middlewares.

Thanks @cryptodeal
I also tested body-parser and it works, but i am stuck with schemator plugin solution for getdirname dependency.

from middlewares.

Only schemator has bug with CJS as it's has dependency called getdirname, once i'll fix that dependency, schemator also will be able use full-compatible Node.js power

from middlewares.

Commit 0ca4a3e fixes this issue completely (or should fix at least)

from middlewares.