-
Notifications
You must be signed in to change notification settings - Fork 54
fix: wasm build issues #256
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
Conversation
WalkthroughThe recent updates across various projects focus on enhancing the TypeScript dependency, upgrading it from version Changes
Sequence Diagram(s)%% No relevant sequence diagrams were generated due to the nature of the changes.
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Outside diff range, codebase verification and nitpick comments (1)
examples/react/react-app/src/dojo/generated/setup.ts (1)
14-14
: Evaluate the use of console logging for debugging.The console log statement for
torii.poseidonHash(["1"])
is useful for debugging, but ensure it does not leak sensitive information and is appropriate for the production environment. Consider using a more robust logging mechanism if needed.
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yaml
is excluded by!**/pnpm-lock.yaml
Files selected for processing (15)
- examples/dojo-starter (1 hunks)
- examples/react/react-app/package.json (2 hunks)
- examples/react/react-app/src/dojo/generated/setup.ts (2 hunks)
- examples/react/react-pwa-app/package.json (1 hunks)
- examples/react/react-threejs/package.json (1 hunks)
- packages/core/package.json (1 hunks)
- packages/create-burner/package.json (1 hunks)
- packages/create-dojo/package.json (1 hunks)
- packages/react/package.json (1 hunks)
- packages/state/package.json (1 hunks)
- packages/torii-client/package.json (1 hunks)
- packages/torii-wasm/build.sh (1 hunks)
- packages/torii-wasm/package.json (1 hunks)
- packages/utils-wasm/package.json (1 hunks)
- packages/utils/package.json (1 hunks)
Files skipped from review due to trivial changes (4)
- examples/dojo-starter
- examples/react/react-app/package.json
- packages/create-burner/package.json
- packages/torii-wasm/build.sh
Additional comments not posted (14)
packages/torii-client/package.json (1)
21-21
: Verify compatibility with TypeScript^5.5.4
.The TypeScript dependency has been updated. Ensure that the codebase is compatible with the new version, as it may introduce breaking changes or new features.
packages/create-dojo/package.json (1)
25-25
: Verify compatibility with TypeScript^5.5.4
.The TypeScript version in the devDependencies has been updated. Ensure that the development environment is compatible with the new version.
packages/state/package.json (1)
21-21
: Verify compatibility with TypeScript^5.5.4
.The TypeScript version in the devDependencies has been updated. Ensure that the codebase is compatible with the new version, as it may introduce breaking changes or new features.
packages/utils-wasm/package.json (1)
27-27
: Verify compatibility with TypeScript 5.5.4.The TypeScript version has been updated. Ensure that the codebase is compatible with this version and that the build process works correctly.
packages/utils/package.json (1)
24-24
: Verify compatibility with TypeScript 5.5.4.The TypeScript version has been updated. Ensure that the codebase is compatible with this version and that the build process works correctly.
packages/core/package.json (1)
27-27
: Verify compatibility with TypeScript 5.5.4.The TypeScript version has been updated. Ensure that the codebase is compatible with this version and that the build process works correctly.
packages/torii-wasm/package.json (4)
7-8
: Approved: Relative path updates.The changes from absolute to relative paths in the
main
,browser
,module
, andtypes
fields improve portability and consistency.Also applies to: 14-15
17-24
: Approved: Explicit file inclusion.Explicitly listing files in the
files
field improves clarity and control over the package's exported content.
27-27
: Approved: Simplified sideEffects.The simplification of the
sideEffects
field to include only theweb
JavaScript file reflects a more modular approach.
31-32
: Verify dependency version changes.The TypeScript update and wasm-pack downgrade may affect the build process. Ensure compatibility with the project's requirements.
packages/react/package.json (1)
34-34
: Approved: TypeScript version update.The update to TypeScript
^5.5.4
likely includes enhancements and bug fixes. Ensure compatibility with the project's requirements.examples/react/react-pwa-app/package.json (1)
52-52
: Approved: TypeScript version update.The update to TypeScript
^5.5.4
likely includes enhancements and bug fixes. Ensure compatibility with the project's requirements.examples/react/react-app/src/dojo/generated/setup.ts (1)
8-8
: Verify the removal ofWeierstrassSignatureType
.Ensure that the removal of
WeierstrassSignatureType
does not affect the functionality elsewhere in the codebase.examples/react/react-threejs/package.json (1)
80-80
: TypeScript version update.The
typescript
dependency has been updated from^5.0.3
to^5.5.4
. Ensure that the project is compatible with this new version, and consider testing for any breaking changes or new features that might affect the codebase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yaml
is excluded by!**/pnpm-lock.yaml
Files selected for processing (2)
- .github/workflows/ci.yaml (1 hunks)
- packages/torii-wasm/package.json (1 hunks)
Files skipped from review due to trivial changes (1)
- .github/workflows/ci.yaml
Files skipped from review as they are similar to previous changes (1)
- packages/torii-wasm/package.json
Summary by CodeRabbit
New Features
Bug Fixes
torii-wasm
package.Chores
torii-wasm
package, improving organization and clarity.Documentation