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
The types ScheduledPublishingPluginOptions and BetaFeatures aren't exported, which makes it impossible to reexport the defineConfig.
To Reproduce
Steps to reproduce the behavior:
I'm working on sanity-typed, so all of these things are within that repo
Update sanity to 3.61.0 (or anything past 3.38.0).
npm install
npm build, watch it break.
(If I go into packages/types/node_modules/sanity/lib/index.d.ts and change declare interface ScheduledPublishingPluginOptions to export interface ScheduledPublishingPluginOptions, everything works)
Expected behavior
For builds re-exporting defineConfig not to break
Screenshots
@sanity-typed/types:build: src/internal.ts(1324,14): error TS4023: Exported variable 'defineConfig' has or is using name 'ScheduledPublishingPluginOptions' from external module "/Users/shayan/Workspace/sanity-typed/node_modules/sanity/lib/index" but cannot be named.
@sanity-typed/types:build: src/internal.ts(1324,14): error TS4023: Exported variable 'defineConfig' has or is using name 'BetaFeatures' from external module "/Users/shayan/Workspace/sanity-typed/node_modules/sanity/lib/index" but cannot be named.
The text was updated successfully, but these errors were encountered:
Describe the bug
The types
ScheduledPublishingPluginOptions
andBetaFeatures
aren't exported, which makes it impossible to reexport thedefineConfig
.To Reproduce
Steps to reproduce the behavior:
I'm working on
sanity-typed
, so all of these things are within that repo3.61.0
(or anything past3.38.0
).npm install
npm build
, watch it break.packages/types/node_modules/sanity/lib/index.d.ts
and changedeclare interface ScheduledPublishingPluginOptions
toexport interface ScheduledPublishingPluginOptions
, everything works)Expected behavior
For builds re-exporting
defineConfig
not to breakScreenshots
The text was updated successfully, but these errors were encountered: