Unable to resolve module @pixi/core

[cdesch]

Unable to resolve module @pixi/core using "expo": "~40.0.0",

Failed building JavaScript bundle.
Unable to resolve module @pixi/core from /Users/cj1/projects/autograph_nft_app/node_modules/@pixi/filter-adjustment/dist/filter-adjustment.cjs.js: @pixi/core could not be found within the project.

If you are sure the module exists, try these steps:
 1. Clear watchman watches: watchman watch-del-all
 2. Delete node_modules and run yarn install
 3. Reset Metro's cache: yarn start --reset-cache
 4. Remove the cache: rm -rf /tmp/metro-*
  10 | Object.defineProperty(exports, '__esModule', { value: true });
  11 |
> 12 | var core = require('@pixi/core');
     |                     ^
  13 |

[guavadevelopment]

Your mileage may vary but I got this to work in expo 40 by adding these modules directly to my project with yarn add

"@pixi/core": "^6.0.0",
"@pixi/filter-alpha": "^6.0.0",
"@pixi/filter-blur": "^6.0.0",

[srmagura]

The problem is in the package.json. expo-pixi is pulling in whatever the latest version of pixi-filters is:

"pixi-filters": "*",

Fixed in my project by forcing pixi-filters to resolve to 3.1.1 with a Yarn resolution in my package.json:

"resolutions": {
    "pixi-filters": "3.1.1"
}

[rbrogi]

Hi, i have the same problem with expo 42.... i tried add "@pixi/core": "^6.0.0", "@pixi/filter-alpha": "^6.0.0", "@pixi/filter-blur": "^6.0.0", & "pixi-filters": "3.1.1"

but nothing...

have you any idea?

[srmagura]

Hey @rbrogi, expo-pixi is super unmaintained and has many issues. I would suggest using something else.

I switched to react-native-signature-canvas. It has its own issues but does ultimately work.

[rbrogi]

@srmagura thanks so musch about the info.

[brentvatne]

we don't currently maintain this library because we don't have the time for it, but if someone would like to contribute and take over maintainership please let me know

[Bartozzz]

@brentvatne @EvanBacon I'd be happy to maintain this package. I created a PR that fixes all of the major issues here. Please, feel free to contact me on hi@laniewski.me if you'd like to discuss. I am a hobbyist game developer, so I'll maintain my fork anyway.

[flyskywhy]

@Bartozzz maybe you can also have a look at https://github.com/flyskywhy/react-native-pixi which also forked from here 😝

[thargenediad]

@brentvatne @EvanBacon I'd be happy to maintain this package. I created a PR that fixes all of the major issues here. Please, feel free to contact me on hi@laniewski.me if you'd like to discuss. I am a hobbyist game developer, so I'll maintain my fork anyway.

@Bartozzz , Is there a way I can use your fork with the Signature component included?
The Signature piece is the only thing I need pixi for.

[Bartozzz]

@thargenediad I could, but I guess there's no point since this repository is dead and I won't have time to maintain my fork on my own. My recommendation for you is to copy my fork directly to your project and add the Signature component on your own – it should be pretty straightforward.