You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removes side-effects by just exporting PIXI instead of messing with the global scope;
Built with expo-module-scripts;
Breaking changes:
It removes Spine, Signature, Sketch and FilterImage. I think it's reasonable for expo-pixi to just add support for pixi.js in Expo and do nothing more. Removed components can be easily reexported to their own packages to prevent the bloating of expo-pixi package. Removing this bloat will also close a lot of issues.
What does it mean that "Removed components can be easily reexported to their own packages..."?
I only need the Signature component to work.
How would I get it to work?
Honestly, I think this repository is dead. I'd recommend you simply copy the source code of my fork directly to your project.
What does it mean that "Removed components can be easily reexported to their own packages..."? I only need the Signature component to work. How would I get it to work?
I wanted to make this package as simple as possible. I decided to just keep the pixi.js abstraction and remove all additional React components, including Signature. Once this is merged, you'd have to copy Signature.js to your project.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a refactor of
expo-pixipackage.It fixes several issues, noticeably:
pixi.jsandpixi-filters:expo-assetandexpo-gl:expo-asset-utils#61 (expo-asset-utilsis no longer needed)Additionally, it adds a few features:
PIXIinstead of messing with the global scope;expo-module-scripts;Breaking changes:
Spine,Signature,SketchandFilterImage. I think it's reasonable forexpo-pixito just add support forpixi.jsin Expo and do nothing more. Removed components can be easily reexported to their own packages to prevent the bloating ofexpo-pixipackage. Removing this bloat will also close a lot of issues.Closes #78
Closes #113