Import issue : You may need an additional loader to handle the result of these loaders.

Question

Import issue : You may need an additional loader to handle the result of these loaders.

jasonakon opened this issue 3 years ago · 15 comments

jasonakon commented 3 years ago

This error message happens right after imported your package

Answer 1 · 2021-06-18T17:17:40.000Z

Are you trying to import it in a nodejs file, or in a frontend js file?

Answer 2 · 2021-06-18T17:26:51.000Z

Hi, in frontend js file

Answer 3 · 2021-06-18T17:35:20.000Z

I had a similar issue about these but I thought it was fixed. Probably is caused by the npm version because in my tests I did not encounter it. Anyway I will remove the optional chaining package asap.

Answer 4 · 2021-06-25T04:31:15.000Z

Thanks for sharing the template. I am encountering the same issue that @jasonakon reported after I imported the package.

Answer 5 · 2021-07-02T15:51:34.000Z

Any update on this issue? When will you be fixing this?

Answer 6 · 2021-07-02T16:09:35.000Z

Yeah, I'll do my best. I think this weekend I'll publish new version.

Answer 7 · 2021-07-07T01:51:27.000Z

Adding stdout text copy paste here for searchability

Error: ./node_modules/jspdf-invoice-template/src/index.js 90:22
Module parse failed: Unexpected token (90:22)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     orientationLandscape: props.orientationLandscape || false,
|     logo: {
>       src: props.logo?.src || "",
|       width: props.logo?.width || "",
|       height: props.logo?.height || "",

Is updating the ECMAScript target sufficient to resolve the modern syntax?

i.e. was the loader issue caused by 3751f8b#diff-b55cdbef4907b7045f32cc5360d48d262cca5f94062e353089f189f4460039e0

The babel plugin would have fixed this?

78e7838#diff-09c56b2bf95de2a608a36afef3b6893146a959d6739be0a154dc9c9f02d80f24

This is related to #2 #2

Answer 8 · 2021-07-07T02:14:19.000Z

I used a quick online transpiler tool to fill the modern syntax into compatible js for those optional chaining accessors etc ./node_modules/jspdf-invoice-template/src/index.js 90:22 to start prototyping with it faster (unreadable code, though).

TypeScript <3

Thank you for the package.
Looking forward to seeing how you update this.

Answer 9 · 2021-07-07T20:36:08.000Z

I used a quick online transpiler tool to fill the modern syntax into compatible js for those optional chaining accessors etc ./node_modules/jspdf-invoice-template/src/index.js 90:22 to start prototyping with it faster (unreadable code, though).

TypeScript <3

Thank you for the package.
Looking forward to seeing how you update this.

Thanks man! I'll do my best. I have been too busy and couldn't do the updates till now. I think and hope these days I'll push them.

Answer 10 · 2021-07-15T21:44:54.000Z

Please, can someone let me know which version of nodejs and npm have you installed?
Cmd commands:
npm -v and node -v

Answer 11 · 2021-07-15T21:58:35.000Z

npm version 6.14.13 and node version 14.17.2

Answer 12 · 2021-07-16T08:07:21.000Z

@bhasshaw please, can you try to update npm and then try if this issue is still present? (I'm trying to understand the issue so I can leave the optional chaining package). Thank you!

Answer 13 · 2021-07-16T17:58:05.000Z

I'm using a .nvmrc file with the node version 14.17.2, that then determines the npm version of 6.14.13 so there is no updating it beyond that.

Answer 14 · 2021-07-28T21:29:07.000Z

I updated node to 16.5.0 and nvm updated npm to 7.19.1 and now it works.

Answer 15 · 2021-08-10T16:30:33.000Z

I'm gonna close this issue due to the fix done in version 1.3.2