adieuadieu / alagarr Goto Github PK

Add a convenience method on the response object to simplify setting headers. See expressjs for inspiration. Method should return same response object for chaining.

Trying to assign a simple response middleware to evaluate GitHub tokens with X-Hub-Signature. Getting an error such as There was an error in the error handler provided to Alagaar TypeError: middleware is not a function at Object.<anonymous> (/var/task/node_modules/alagarr/dist/src/utils/apply-middleware.js:13:117)

Applying it with a config like {responseMiddleware: ['default', validateSignature]}

Using node 8.10 on AWS Lambda

in combination with https://github.com/marionebl/commitlint ?

Add an example handler which includes/demonstrates routing with a router like franxx or trouter

add request middleware to support parsing of multipart/form-data request body

Is the latest version published to the npm?

I am just wondering because of this handler:

export const myFunction = alagarr(async (request, response) => {
  try {
    const data = await data();
    return response.json(data);
  } catch (error) {
    throw new ClientError(error);
  }
});

gives me a warning:

Serverless: Warning: handler 'myFunction' returned a promise and also uses a callback!
This is problematic and might cause issues in your lambda.

Is this bug in the library or is the npm version older?

npm install alagarr --save install version ^1.0.0-26 and, if I try to install directly from GitHub the dist folder is empty, so I cant test directly from the master.

However, thanks for the great library.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• ⬆️ Update dependency @types/node to v18
• ⬆️ Update dependency husky to v8
• ⬆️ Update dependency lint-staged to v13
• ⬆️ Update dependency rimraf to v4
• ⬆️ Update dependency typescript to v5
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• ⬆️ Update dependency @types/aws-lambda to v8.10.114
• ⬆️ Update dependency @types/jest to v23.3.14
• ⬆️ Update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• ⬆️ Update dependency semantic-release to v17 [SECURITY]
• ⬆️ Update dependency tslint to v5.20.1
• ⬆️ Update dependency typescript to v3.9.10
• ⬆️ Update commitlint monorepo to v17 (major) (@commitlint/cli, @commitlint/config-conventional)
• ⬆️ Update dependency nyc to v15
• ⬆️ Update dependency prettier to v2
• ⬆️ Update dependency tslint-functional-preset to v2

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Add a convenience method on the response object to simplify setting cookies. See expressjs for inspiration. Method should return same response object for chaining.

Refactor some middleware into factories, e.g. middleware=[ csp({ options }), other(), etc]

• CSP middleware, to allow configuration of content security policies
• what else?

etag response middleware

set connect-src, default-src, form-action csp rules

add convenience context.callbackWaitsForEmptyEventLoop=false middleware

On registry https://registry.npmjs.org/, the "latest" version (v3.2.1) of dependency nsp has the following deprecation notice:

The Node Security Platform service is shutting down 9/30 - https://blog.npmjs.org/post/175511531085/the-node-security-platform-service-is-shutting

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about nsp's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Add a request middleware which verifies safety of headers. E.g.

☐ Verify that header values in both requests and responses contain only ASCII characters

Extend response.respondTo() to accept function, rather than than just string. This allows for only computing the response required to satisfy the Accept header. See expressjs for inspiration.

• implement it
• update documentation
• update default error handler to make use of it

return an object from handler, automatically returned to response.json() or response.respondTo() if return { json: {}, html: '' }

easily respond with images/binary data (some API Gateway setup required..)

all security headers described here by default

Overload response method function signatures to support: (body, statusCode, options), (statusCode, body, options), (body, options, statusCode)

E.g. in src/types.ts

export interface InterfaceResponse {
  /**
   * Redirect to a new location.
   */
  readonly redirect: (
    location: string,
    statusCode?: number,
    options?: InterfaceResponseOptions,
  ) => void

  ...

}

rollup-plugin-typescript2?