* An instance of the Medusa JS Client. If you don't provide an instance, one will be created using the `baseUrl`, `apiKey`, `publishableApiKey`, `maxRetries`, and `customHeaders` props.
* An instance of the Medusa JS Client. If you don't provide an instance, one will be created using the `baseUrl`, `apiKey`,
* `publishableApiKey`, `maxRetries`, and `customHeaders` props.
* The name of the session ID cookie to set in the response (and read from in the request). The default value is `connect.sid`.
* The name of the session ID cookie to set in the response (and read from in the request). The default value is `connect.sid`.
* Refer to [express-session’s documentation](https://www.npmjs.com/package/express-session#name) for more details.
*/
name?: string
@@ -27,7 +27,7 @@ type SessionOptions = {
*/
rolling?: boolean
/**
* Whether a session that is "uninitialized" is forced to be saved to the store. The default value is `true`.
* Whether a session that is "uninitialized" is forced to be saved to the store. The default value is `true`.
* Refer to [express-session’s documentation](https://www.npmjs.com/package/express-session#saveUninitialized) for more details.
*/
saveUninitialized?: boolean
@@ -45,7 +45,7 @@ type SessionOptions = {
/**
* @interface
*
*
* HTTP compression configurations.
*/
exporttypeHttpCompressionOptions={
@@ -54,17 +54,17 @@ export type HttpCompressionOptions = {
*/
enabled?: boolean
/**
* The level of zlib compression to apply to responses. A higher level will result in better compression but will take longer to complete.
* The level of zlib compression to apply to responses. A higher level will result in better compression but will take longer to complete.
* A lower level will result in less compression but will be much faster. The default value is `6`.
*/
level?: number
/**
* How much memory should be allocated to the internal compression state. It's an integer in the range of 1 (minimum level) and 9 (maximum level).
* How much memory should be allocated to the internal compression state. It's an integer in the range of 1 (minimum level) and 9 (maximum level).
* The default value is `8`.
*/
memLevel?: number
/**
* The minimum response body size that compression is applied on. Its value can be the number of bytes or any string accepted by the
* The minimum response body size that compression is applied on. Its value can be the number of bytes or any string accepted by the
* [bytes](https://www.npmjs.com/package/bytes) module. The default value is `1024`.
*/
threshold?: number|string
@@ -72,36 +72,36 @@ export type HttpCompressionOptions = {
/**
* @interface
*
*
* Essential configurations related to the Medusa backend, such as database and CORS configurations.
*/
exporttypeProjectConfigOptions={
/**
* The Medusa backend’s API Routes are protected by Cross-Origin Resource Sharing (CORS). So, only allowed URLs or URLs matching a specified pattern can send requests to the backend’s API Routes.
*
* `store_cors` is a string used to specify the accepted URLs or patterns for store API Routes. It can either be one accepted origin, or a comma-separated list of accepted origins.
*
*
* `store_cors` is a string used to specify the accepted URLs or patterns for store API Routes. It can either be one accepted origin, or a comma-separated list of accepted origins.
*
* Every origin in that list must either be:
*
*
* 1. A URL. For example, `http://localhost:8000`. The URL must not end with a backslash;
* 2. Or a regular expression pattern that can match more than one origin. For example, `.example.com`. The regex pattern that the backend tests for is `^([\/~@;%#'])(.*?)\1([gimsuy]*)$`.
*
*
* @example
* Some example values of common use cases:
*
*
* ```bash
* # Allow different ports locally starting with 800
* STORE_CORS=/http:\/\/localhost:800\d+$/
*
*
* # Allow any origin ending with vercel.app. For example, storefront.vercel.app
* STORE_CORS=/vercel\.app$/
*
*
* # Allow all HTTP requests
* STORE_CORS=/http:\/\/.+/
* ```
*
*
* Then, set the configuration in `medusa-config.js`:
*
*
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
@@ -111,9 +111,9 @@ export type ProjectConfigOptions = {
* // ...
* }
* ```
*
*
* If you’re adding the value directly within `medusa-config.js`, make sure to add an extra escaping `/` for every backslash in the pattern. For example:
*
*
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
@@ -127,30 +127,30 @@ export type ProjectConfigOptions = {
store_cors?: string
/**
* The Medusa backend’s API Routes are protected by Cross-Origin Resource Sharing (CORS). So, only allowed URLs or URLs matching a specified pattern can send requests to the backend’s API Routes.
*
* `admin_cors` is a string used to specify the accepted URLs or patterns for admin API Routes. It can either be one accepted origin, or a comma-separated list of accepted origins.
*
*
* `admin_cors` is a string used to specify the accepted URLs or patterns for admin API Routes. It can either be one accepted origin, or a comma-separated list of accepted origins.
*
* Every origin in that list must either be:
*
*
* 1. A URL. For example, `http://localhost:7001`. The URL must not end with a backslash;
* 2. Or a regular expression pattern that can match more than one origin. For example, `.example.com`. The regex pattern that the backend tests for is `^([\/~@;%#'])(.*?)\1([gimsuy]*)$`.
*
*
* @example
* Some example values of common use cases:
*
*
* ```bash
* # Allow different ports locally starting with 700
* ADMIN_CORS=/http:\/\/localhost:700\d+$/
*
*
* # Allow any origin ending with vercel.app. For example, admin.vercel.app
* ADMIN_CORS=/vercel\.app$/
*
*
* # Allow all HTTP requests
* ADMIN_CORS=/http:\/\/.+/
* ```
*
*
* Then, set the configuration in `medusa-config.js`:
*
*
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
@@ -160,9 +160,9 @@ export type ProjectConfigOptions = {
* // ...
* }
* ```
*
*
* If you’re adding the value directly within `medusa-config.js`, make sure to add an extra escaping `/` for every backslash in the pattern. For example:
*
*
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
@@ -176,10 +176,10 @@ export type ProjectConfigOptions = {
admin_cors?: string
/**
* A random string used to create cookie tokens. Although this configuration option is not required, it’s highly recommended to set it for better security.
*
* In a development environment, if this option is not set, the default secret is `supersecret` However, in production, if this configuration is not set, an error is thrown and
*
* In a development environment, if this option is not set, the default secret is `supersecret` However, in production, if this configuration is not set, an error is thrown and
* the backend crashes.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
@@ -196,10 +196,10 @@ export type ProjectConfigOptions = {
/**
* A random string used to create authentication tokens. Although this configuration option is not required, it’s highly recommended to set it for better security.
*
*
* In a development environment, if this option is not set the default secret is `supersecret` However, in production, if this configuration is not set an error, an
* error is thrown and the backend crashes.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
@@ -216,15 +216,15 @@ export type ProjectConfigOptions = {
/**
* The name of the database to connect to. If specified in `database_url`, then it’s not required to include it.
*
* Make sure to create the PostgreSQL database before using it. You can check how to create a database in
*
* Make sure to create the PostgreSQL database before using it. You can check how to create a database in
* - `[user]`: (required) your PostgreSQL username. If not specified, the system's username is used by default. The database user that you use must have create privileges. If you're using the `postgres` superuser, then it should have these privileges by default. Otherwise, make sure to grant your user create privileges. You can learn how to do that in [PostgreSQL's documentation](https://www.postgresql.org/docs/current/ddl-priv.html).
* - `[:password]`: an optional password for the user. When provided, make sure to put `:` before the password.
* - `[host]`: (required) your PostgreSQL host. When run locally, it should be `localhost`.
* - `[:post]`: an optional port that the PostgreSQL server is listening on. By default, it's `5432`. When provided, make sure to put `:` before the port.
* - `[dbname]`: (required) the name of the database.
*
*
* You can learn more about the connection URL format in [PostgreSQL’s documentation](https://www.postgresql.org/docs/current/libpq-connect.html).
*
*
* @example
* For example, set the following database URL in your environment variables:
@@ -273,11 +273,11 @@ export type ProjectConfigOptions = {
database_url?: string
/**
* The database schema to connect to. This is not required to provide if you’re using the default schema, which is `public`.
*
*
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
* database_schema: process.env.DATABASE_SCHEMA ||
* database_schema: process.env.DATABASE_SCHEMA ||
* "custom",
* // ...
* },
@@ -289,13 +289,13 @@ export type ProjectConfigOptions = {
/**
* This configuration specifies what database messages to log. Its value can be one of the following:
*
*
* - (default) A boolean value that indicates whether any messages should be logged.
* - The string value `all` that indicates all types of messages should be logged.
* - An array of log-level strings to indicate which type of messages to show in the logs. The strings can be `query`, `schema`, `error`, `warn`, `info`, `log`, or `migration`. Refer to [Typeorm’s documentation](https://typeorm.io/logging#logging-options) for more details on what each of these values means.
*
*
* If this configuration isn't set, its default value is `false`, meaning no database messages are logged.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
@@ -314,24 +314,24 @@ export type ProjectConfigOptions = {
/**
* @ignore
* @deprecated
*
*
* @privateRemark
* only postgres is supported, so this config has no effect
*/
database_type?: string
/**
* An object that includes additional configurations to pass to the database connection. You can pass any configuration. One defined configuration to pass is
* An object that includes additional configurations to pass to the database connection. You can pass any configuration. One defined configuration to pass is
* `ssl` which enables support for TLS/SSL connections.
*
* This is useful for production databases, which can be supported by setting the `rejectUnauthorized` attribute of `ssl` object to `false`.
*
* This is useful for production databases, which can be supported by setting the `rejectUnauthorized` attribute of `ssl` object to `false`.
* During development, it’s recommended not to pass this option.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
* database_extra:
* database_extra:
* process.env.NODE_ENV !== "development"
* ? { ssl: { rejectUnauthorized: false } }
* : {},
@@ -345,7 +345,7 @@ export type ProjectConfigOptions = {
/**
* Configure support for TLS/SSL connection
*/
ssl:{
ssl:{
/**
* Whether to fail connection if the server certificate is verified against the list of supplied CAs and the hostname and no match is found.
*/
@@ -355,26 +355,26 @@ export type ProjectConfigOptions = {
/**
* Used to specify the URL to connect to Redis. This is only used for scheduled jobs. If you omit this configuration, scheduled jobs won't work.
*
*
* :::note
*
*
* You must first have Redis installed. You can refer to [Redis's installation guide](https://redis.io/docs/getting-started/installation/).
*
*
* :::
*
*
* The Redis connection URL has the following format:
* For a local Redis installation, the connection URL should be `redis://localhost:6379` unless you’ve made any changes to the Redis configuration during installation.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
* redis_url: process.env.REDIS_URL ||
* redis_url: process.env.REDIS_URL ||
* "redis://localhost:6379",
* // ...
* },
@@ -385,15 +385,15 @@ export type ProjectConfigOptions = {
redis_url?: string
/**
* The prefix set on all keys stored in Redis. The default value is `sess:`.
*
* The prefix set on all keys stored in Redis. The default value is `sess:`.
*
* If this configuration option is provided, it is prepended to `sess:`.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
* redis_prefix: process.env.REDIS_PREFIX ||
* redis_prefix: process.env.REDIS_PREFIX ||
* "medusa:",
* // ...
* },
@@ -404,15 +404,15 @@ export type ProjectConfigOptions = {
redis_prefix?: string
/**
* An object of options to pass ioredis. You can refer to [ioredis’s RedisOptions documentation](https://redis.github.io/ioredis/index.html#RedisOptions)
* An object of options to pass ioredis. You can refer to [ioredis’s RedisOptions documentation](https://redis.github.io/ioredis/index.html#RedisOptions)
@@ -425,13 +425,13 @@ export type ProjectConfigOptions = {
/**
* An object of options to pass to [express-session](https://www.npmjs.com/package/express-session).
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig: {
* session_options: {
* name: process.env.SESSION_NAME ||
* name: process.env.SESSION_NAME ||
* "custom",
* },
* // ...
@@ -443,13 +443,13 @@ export type ProjectConfigOptions = {
session_options?: SessionOptions
/**
* Configure HTTP compression from the application layer. If you have access to the HTTP server, the recommended approach would be to enable it there.
* Configure HTTP compression from the application layer. If you have access to the HTTP server, the recommended approach would be to enable it there.
* However, some platforms don't offer access to the HTTP layer and in those cases, this is a good alternative.
*
*
* Its value is an object that has the following properties:
*
*
* If you enable HTTP compression and you want to disable it for specific API Routes, you can pass in the request header `"x-no-compression": true`.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
@@ -469,8 +469,8 @@ export type ProjectConfigOptions = {
http_compression?: HttpCompressionOptions
/**
* Configure the number of staged jobs that are polled from the database. Default is 1000.
*
* Configure the number of staged jobs that are polled from the database. Default is `1000`.
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
@@ -487,18 +487,18 @@ export type ProjectConfigOptions = {
/**
* @interface
*
*
* The configurations for your Medusa backend are in `medusa-config.js` located in the root of your Medusa project. The configurations include database, modules, and plugin configurations, among other configurations.
*
*
* `medusa-config.js` exports an object having the following properties:
*
*
* - {@link ConfigModule.projectConfig | projectConfig}: (required): An object that holds general configurations related to the Medusa backend, such as database or CORS configurations.
* - {@link ConfigModule.plugins | plugins}: An array of plugin configurations that defines what plugins are installed and optionally specifies each of their configurations.
* - {@link ConfigModule.modules | modules}: An object that defines what modules are installed and optionally specifies each of their configurations.
* - {@link ConfigModule.featureFlags | featureFlags}: An object that enables or disables features guarded by a feature flag.
*
*
* For example:
*
*
* ```js title="medusa-config.js"
* module.exports = {
* projectConfig,
@@ -507,16 +507,16 @@ export type ProjectConfigOptions = {
* featureFlags,
* }
* ```
*
*
* ---
*
*
* ## Environment Variables
*
*
* It's highly recommended to store the values of configurations in environment variables, then reference them within `medusa-config.js`.
*
* During development, you can set your environment variables in the `.env` file at the root of your Medusa backend project. In production,
*
* During development, you can set your environment variables in the `.env` file at the root of your Medusa backend project. In production,
* setting the environment variables depends on the hosting provider.
*
*
* ---
*/
exporttypeConfigModule={
@@ -526,18 +526,18 @@ export type ConfigModule = {
projectConfig: ProjectConfigOptions
/**
* On your Medusa backend, you can use [Plugins](https://docs.medusajs.com/development/plugins/overview) to add custom features or integrate third-party services.
* On your Medusa backend, you can use [Plugins](https://docs.medusajs.com/development/plugins/overview) to add custom features or integrate third-party services.
* For example, installing a plugin to use Stripe as a payment processor.
*
*
* Aside from installing the plugin with NPM, you need to pass the plugin you installed into the `plugins` array defined in `medusa-config.js`.
*
*
* The items in the array can either be:
*
*
* - A string, which is the name of the plugin to add. You can pass a plugin as a string if it doesn’t require any configurations.
* - An object having the following properties:
* - `resolve`: The name of the plugin.
* - `options`: An object that includes the plugin’s options. These options vary for each plugin, and you should refer to the plugin’s documentation for available options.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
@@ -546,7 +546,7 @@ export type ConfigModule = {
* {
* resolve: `medusa-my-plugin`,
* options: {
* apiKey: process.env.MY_API_KEY ||
* apiKey: process.env.MY_API_KEY ||
* `test`,
* },
* },
@@ -565,13 +565,13 @@ export type ConfigModule = {
)[]
/**
* In Medusa, commerce and core logic are modularized to allow developers to extend or replace certain [modules](https://docs.medusajs.com/development/modules/overview)
* In Medusa, commerce and core logic are modularized to allow developers to extend or replace certain [modules](https://docs.medusajs.com/development/modules/overview)
* with custom implementations.
*
*
* Aside from installing the module with NPM, you must add it to the exported object in `medusa-config.js`.
*
*
* The keys of the `modules` configuration object refer to the type of module. Its value can be one of the following:
*
*
* 1. A boolean value indicating whether the module type is enabled;
* 2. Or a string value indicating the name of the module to be used for the module type. This can be used if the module does not require any options;
* 3. Or an object having the following properties, but typically you would mainly use the `resolve` and `options` properties only:
@@ -580,7 +580,7 @@ export type ConfigModule = {
* 3. `resources`: a string indicating whether the module shares the dependency container with the Medusa core. Its value can either be `shared` or `isolated`. Refer to the [Modules documentation](https://docs.medusajs.com/development/modules/create#module-scope) for more details.
* 4. `alias`: a string indicating a unique alias to register the module under. Other modules can’t use the same alias.
* 5. `main`: a boolean value indicating whether this module is the main registered module. This is useful when an alias is used.
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
@@ -590,7 +590,7 @@ export type ConfigModule = {
* },
* cacheService: {
* resolve: "@medusajs/cache-redis",
* options: {
* options: {
* redisUrl: process.env.CACHE_REDIS_URL,
* ttl: 30,
* },
@@ -608,16 +608,16 @@ export type ConfigModule = {
/**
* Some features in the Medusa backend are guarded by a feature flag. This ensures constant shipping of new features while maintaining the engine’s stability.
*
* You can specify whether a feature should or shouldn’t be used in your backend by enabling its feature flag. Feature flags can be enabled through either environment
*
* You can specify whether a feature should or shouldn’t be used in your backend by enabling its feature flag. Feature flags can be enabled through either environment
* variables or through this configuration exported in `medusa-config.js`.
*
*
* If you want to use the environment variables method, learn more about it in the [Feature Flags documentation](https://docs.medusajs.com/development/feature-flags/toggle#method-one-using-environment-variables).
*
*
* The `featureFlags` configuration is an object. Its properties are the names of the feature flags. Each property’s value is a boolean indicating whether the feature flag is enabled.
*
*
* You can find available feature flags and their key name [here](https://github.com/medusajs/medusa/tree/master/packages/medusa/src/loaders/feature-flags).
*
*
* @example
* ```js title="medusa-config.js"
* module.exports = {
@@ -628,11 +628,11 @@ export type ConfigModule = {
* // ...
* }
* ```
*
*
* :::note
*
*
* After enabling a feature flag, make sure to [run migrations](https://docs.medusajs.com/development/entities/migrations/overview#migrate-command) as it may require making changes to the database.
*
*
* :::
*/
featureFlags: Record<string,boolean|string>
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Shahed Nasser
GitHub