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

Setting graphic.interactive = true, gives errors #28

Open
mmmintdesign opened this issue Oct 17, 2022 · 10 comments
Open

Setting graphic.interactive = true, gives errors #28

mmmintdesign opened this issue Oct 17, 2022 · 10 comments

Comments

@mmmintdesign
Copy link

Setting graphic.interactive = true, gives errors
image

@ivanpopelyshev
Copy link
Contributor

That's double-pixi error. graphics-smooth minimal requirement is 6.0.4 and you put something like 6.0.1 in packagejson , right? If not, anyway, remove your packagelock node_modules and install everything again.

@mmmintdesign
Copy link
Author

mmmintdesign commented Oct 17, 2022

That's double-pixi error. graphics-smooth minimal requirement is 6.0.4 and you put something like 6.0.1 in packagejson , right? If not, anyway, remove your packagelock node_modules and install everything again.

The version is at 6.5.6. I've tried multiple times to delete/reinstall node_modules and package-lock.json.
Not sure if I'm doing something wrong. I'll try it on another computer.

@ivanpopelyshev
Copy link
Contributor

Please provide your demo, webpack-knowledgable people should point what's the problem )

@mmmintdesign
Copy link
Author

Not sure what's the best way to share a demo, but here is repo: https://github.com/mmmintdesign/pixi-demo

@ivanpopelyshev
Copy link
Contributor

I looked at the demo and I dont understand whats wrong with interaction. @bigtimebuddy can you please look at it?

@bigtimebuddy
Copy link
Contributor

This worked fine for me: https://codesandbox.io/s/eager-napier-88ev5c

I think this is a Webpack issue.

@ivanpopelyshev
Copy link
Contributor

Now I remember! Yes, it can be webpack issue, there was one not long ago. Please update webpack to latest.

@bigtimebuddy
Copy link
Contributor

Obviously, use whatever tools meet your needs, but I think Parcel is more usable out-of-the-box and faster. Would highly recommend over Webpack.

@mmmintdesign
Copy link
Author

Updated Webpack and all related packages, still getting the bug.

Just used to Webpack, might have to switch to Parcel

@ivanpopelyshev
Copy link
Contributor

Ugh, those bundlers, ughhhhh

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