-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fresh install doesn't work #132
Comments
@EmilyYond I believe I ran into the same issue as you here. I was able to resolve this quickly by rolling back More contextI generated fresh plugin files from the command: npx @sanity/plugin-kit init sanity-plugin-name Output:dependencies:
+ @sanity/incompatible-plugin 1.0.4
devDependencies:
+ @sanity/pkg-utils 5.1.4
+ @sanity/plugin-kit 3.1.10
+ @types/react 18.2.70
+ @typescript-eslint/eslint-plugin 7.3.1
+ @typescript-eslint/parser 7.3.1
+ eslint 8.57.0
+ eslint-config-prettier 9.1.0
+ eslint-config-sanity 7.1.2
+ eslint-plugin-prettier 5.1.3
+ eslint-plugin-react 7.34.1
+ eslint-plugin-react-hooks 4.6.0
+ npm-run-all 4.1.5
+ prettier 3.2.5
+ prettier-plugin-packagejson 2.4.12
+ react 18.2.0
+ react-dom 18.2.0
+ react-is 18.2.0
+ rimraf 5.0.5
+ sanity 3.35.2
+ styled-components 5.3.11 (6.1.8 is available)
+ typescript 5.4.3
WARN Issues with peer dependencies found
.
└─┬ @sanity/pkg-utils 5.1.4
└── ✕ unmet peer typescript@5.4.2: found 5.4.3
Done in 20.2s
[info] Done! First stepsI first checked the WARN Issues with peer dependencies found
.
└─┬ @sanity/pkg-utils 5.1.4
└── ✕ unmet peer typescript@5.4.2: found 5.4.3 This being a warning I didn't think was the cause of the issue but it did encourage me to check I came across this in the change log:
ResolutionTesting to see if this would resolve the build error I pinned ...
"resolutions": {
"@sanity/pkg-utils": "5.1.0",
},
... Once this change was made I reinstalled my packages and attempted to build the plugin again and it worked! ClarificationThis is definitely not a long-term solution as you'll have to pin Hope this is helpful for anyone who comes across this issue as well 🙂 |
I have tried multiple times using
npx @sanity/plugin-kit init pluginname
, following the wizard, and then when runningyarn build
it instantly fails (see screenshot below)All your plugin docs suggest using this but it doesn't work out of the box, so its not a great starting point! Please could someone take a look?
The text was updated successfully, but these errors were encountered: