forked from sanity-io/sanity
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpnpm-workspace.yaml
More file actions
80 lines (74 loc) · 2.25 KB
/
pnpm-workspace.yaml
File metadata and controls
80 lines (74 loc) · 2.25 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
packages:
- dev/*
- perf/*
- examples/*
- scripts
- e2e
- packages/@repo/*
- packages/@sanity/*
- packages/create-sanity
- packages/groq
- packages/sanity
- packages/sanity/fixtures/examples/*
catalog:
'@playwright/experimental-ct-react': 1.56.1
'@playwright/test': 1.56.1
'@sanity/client': ^7.12.1
'@sanity/eslint-config-i18n': ^2.0.0
'@sanity/pkg-utils': ^8.1.13
'@sanity/ui': ^3.1.5
'@sanity/ui-workshop': ^3.1.2
'@types/node': ^24.3.0
'@types/react': ^19.1.9
'@types/react-dom': ^19.1.7
'@types/react-is': ^19.0.0
'@vitejs/plugin-react': ^4.6.0
esbuild: 0.27.0
esbuild-register: ^3.6.0
eslint: ^9.37.0
globals: ^16.2.0
playwright: 1.56.1
prettier: ^3.6.2
react: ^19.1.1
react-dom: ^19.1.1
react-is: ^19.1.1
# Note: there is currently a test failure in src/core/form/inputs/files/FileInput/__tests__/fileInput.test.tsx
# that blocks us from upgrading to jsdom@27 – once that test is passing, the jsdom override can be removed from
# the workspace package.json.
# The test failure looks like this:
# × FileInput with empty state > renders the browse button with a tooltip when it has at least one element in assetSources
# → Cannot create property 'border-width' on string '1px solid var(--card-border-color)'
jsdom: ^26.1.0
vite: ^7.1.7
vitest: ^3.2.4
styled-components: ^6.1.18
typescript: 5.9.3
overrides:
# The e2e-ui.yml workflow needs a @sanity/ui related override in the root package.json in order for it's pnpm add -w ./artifacts/sanity-ui-*.tgz to work its magic.
'@sanity/ui@3': '$@sanity/ui'
# We are currently blocked from upgrading to jsdom 27 because of a strange build error related to the new version of
# cssstyle required by jsdom 27. If this error is no longer present, it's safe to remove the following override.
jsdom: 26.1.0
vitest: $vitest
peerDependencyRules:
allowAny:
- 'react'
- 'react-dom'
catalogs:
react18:
react: ^18.3.1
react-dom: ^18.3.1
preferWorkspacePackages: true
linkWorkspacePackages: deep
minimumReleaseAge: 4320
minimumReleaseAgeExclude:
- '@oxlint/*'
- '@oxlint-tsgolint/*'
- '@portabletext/*'
- '@sanity/*'
- 'groq-js'
- 'oxlint'
- 'oxlint-tsgolint'
- 'eslint-plugin-oxlint'
- 'react-rx'
- 'use-effect-event'