Closed aekiratli closed 6 months ago
@aekiratli it's related to last release in rpc-websocket package.
Currently, we can use create-solana-dapp locally, following to https://github.com/solana-developers/create-solana-dapp/blob/main/CONTRIBUTING.md .
I fixed issue with adding 'rpc-websockets': '7.11.0',
to packages/preset-common/src/utils/package-versions.ts
Looks like
export const packageVersion = {
'@coral-xyz': {
anchor: '^0.30.0',
},
'@tailwindcss': {
typography: '0.5.13',
},
'rpc-websockets': '7.11.0',
'@solana': {
'spl-token': '0.4.6',
'wallet-adapter-base': '^0.9.23',
'wallet-adapter-react': '^0.15.35',
'wallet-adapter-react-ui': '^0.9.35',
'web3.js': '1.91.8',
},
After that I deployed to local yarn registry and run package as described in CONTRIBUTING guide.
Hey @aekiratli and @uafrontender, I reproduced the issue locally and will look at pushing out a fix.
Hey, I think rpc-websockets 7.11.0 will get deprecated: https://github.com/elpheria/rpc-websockets/pull/161
The fix for this issue is open: https://github.com/solana-labs/solana-web3.js/pull/2758
+1 we see this issue as well
+1 we see this issue as well
Probably everyone sees it, I confirmed it here https://github.com/solana-developers/create-solana-dapp/issues/69#issuecomment-2144902641
No need to +1
The fix got released to support the new version with the cjs imports: https://github.com/solana-labs/solana-web3.js/releases/tag/v1.91.9
$ pnpx create-solana-dapp@latest rpc-error
┌ create-solana-dapp 3.0.0
│
◆ Project name: rpc-error
│
◇ Select a preset
│ Next.js
│
◇ Select a UI library
│ Tailwind
│
◇ Select an Anchor template
│ Do not include Anchor in the project
│
◇ Successfully created workspace with pnpm.
│
◇ Successfully installed preset @solana-developers/preset-next@3.0.0.
│
◇ Installation successful! ───────────────────────────╮
│ │
│ That's it! │
│ │
│ Change to your new directory and start developing: │
│ │
│ cd ./rpc-error │
│ │
│ Start the Next.js app: │
│ │
│ pnpm run dev │
│ │
├──────────────────────────────────────────────────────╯
│
└ Good luck with your project!
The issue with @sonala/web3.js is now fixed, and the CLI seems to work again.
Sorry for commenting after the issue was closed. I noticed that the yarn.lock file still references the problematic version. Shouldn't it be updated? The reference can be found here:
@kox you are right. We can now use package but created next.js app still has old version of @solana/web3.js package in its package.json
@beeman should we create new issue?
@kox you are right. We can now use package but created next.js app still has old version of @solana/web3.js package in its package.json
@beeman should we create new issue?
Either start a new app, or update the version manually. It's not something we'll fix in the CLI.
After manually updating package.json
, you can nuke the yarn.lock
, package-lock.json
, or pnpm-lock.yaml
and run the package install again and it should pull in the right version.
To be sure, I pushed v3.0.1 which has the updated package version.