
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
cors-extends
Advanced tools
Cors-Extend is a package which provides the configuration to the existing Cors nodejs package and which enables to configure cors according to the environments.
$ npm install cors-extends
import cors from "cors";
import { corsExtends } from "cors-extend";
cors(
corsExtends({
env: {
development: {
origins: [
{
origin: "http://localhost:3000",
methods: ["GET"],
},
],
routes: [
{
endpoint: "/characters",
methods: ["GET", "POST"],
origins: ["http://localhost:5000"],
},
],
},
},
global: {
blockHttpClient: true,
},
}),
);
Cors-Extend is capable of loading specific configuration according to Environment variable, ENVIRONMENT. The variable can be pass either by dotenv cli, .env file or any other way.
Note
that both environment variable value and configuration name should be equal*
After configuring environment variable in configuration file under the env object specify the environment name
cors(corsExtends({
env{
development:{
}
}
}))
The endpoints can be configured in two ways
By using this configuration we can specify the origins and methods that are allowed for that origins, for the entire application.
origins is an array of object which has a template of
{
origin:"Origin Name",
methods:["GET","POST","PUT","DELETE","PATCH"]
}
Example:
env: {
development: {
origins: [
{
origin: "http://localhost:3000",
methods: ["GET"],
},
];
}
}
So, according to the above configuration the application will only accept GET requests from the client http://localhost:3000
Note
When the origins param or configuration for the certain environment is unspecified, all the requests from all origins will be accepted (Not recommended).
Routes configuration is used to specify the cors configuration for certain routes.
routes is an array of object which has a template of
Property | Type | Optional | Description |
---|---|---|---|
endpoint | String | false | Specify the Route that needs to be configured |
methods | String[] | true | Specify the Methods that would be allowed to the route |
origins | String[] | false | Specify the Origins that would be allowed to the route |
blockHttpClient | Boolean | true | Specify whether to block requests from non Browser Clients |
Example:
env: {
development: {
origins: [
{
endpoint: "/route",
methods: ["GET","POST"],
origins: [
"http://localhost:1000",
"http://web.sankalpafernando"
],
blockHttpClient: false,
},
];
}
}
FAQs
Configure the Cors Options with Ease
The npm package cors-extends receives a total of 0 weekly downloads. As such, cors-extends popularity was classified as not popular.
We found that cors-extends demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.