A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
A utility function to define the StudioCMS config object.
This function is used to define the optional StudioCMS
config object in the Astro project root. The expected file
name is studiocms.config.mjs. And it should be adjacent
to the Astro project's astro.config.mjs file.
StudioCMS will attempt to import this file and use the default
export as the StudioCMS config object automatically if it exists.
Using this function is optional, but it can be useful for IDEs
to provide better intellisense and type checking.
@example
// studiocms.config.mjs
import { defineStudioCMSConfig } from'studiocms';
exportdefaultdefineStudioCMSConfig({
dbStartPage:true,
contentRenderer:'marked',
verbose:true,
dateLocale:'en-us',
// ...Other Options
})
defineStudioCMSConfig({
dashboardConfig:{
Error ts(2353) ― Object literal may only specify known properties, and 'dashboardConfig' does not exist in type '{ plugins?: StudioCMSPlugin[] | undefined; logLevel?: "All" | "Fatal" | "Error" | "Warning" | "Info" | "Debug" | "Trace" | "None" | undefined; dbStartPage?: boolean | undefined; verbose?: boolean | undefined; componentRegistry?: Record<...> | undefined; locale?: { ...; } | undefined; features?: { ...; } | undefined; }'.
