Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail on compilation in Nuxt #2

Open
timothee-durand opened this issue Feb 16, 2022 · 2 comments
Open

Fail on compilation in Nuxt #2

timothee-durand opened this issue Feb 16, 2022 · 2 comments

Comments

@timothee-durand
Copy link

Hello,

To begin thanks for your work !

I've one problem with this package. When I try to use it with Nuxt I've some compilation errors.
OS : windows 11
Nuxt : 2.15
In the terminal :

 ERROR  in ./node_modules/@georgedoescode/generative-utils/dist/index.js                                                      friendly-errors 21:00:32  

Module parse failed: Unexpected token (1:6477)                                                                                friendly-errors 21:00:32  
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
> var Ji=Object.create;var on=Object.defineProperty;var to=Object.getOwnPropertyDescriptor;var eo=Object.getOwnPropertyNames;var no=Object.getPrototypeO
f,ro=Object.prototype.hasOwnProperty;var io=t=>on(t,"__esModule",{value:!0});var U=(t,e)=>()=>(e||t((e={exports:{}}).exports,e),e.exports);var oo= ...

(and all the file directly in the terminal)

And in the browser :

SyntaxError
Unexpected token 'export'

If you can help me I'll be glad to give more informations !
Thanks by advance !

@malwayson
Copy link

Same issue in NextJs as well. I have tried changing the vertion but facing the same issue

@georgedoescode
Copy link
Owner

Hey, sorry to hear about this. It's been a while since I have looked at this library, so a couple of issues fell by the wayside.

I am currently rewriting the library from the ground up, with much better bundling than before. I'm sure this will fix this issue.

In the meantime, I honestly don't plan to make any updates to the existing version. I think the best bet would be to pull the functions you need directly from the repository. Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants