@torpor/build 0.2.0 → 0.3.1

package/dist/response-D-XpIuMH.js

@@ -0,0 +1,307 @@
+import { response, transfer } from "./seeOther-BmehiI4C.js";
+
+//#region src/response/badRequest.ts
+/**
+* 400 Bad Request
+*
+* The HTTP 400 Bad Request client error response status code indicates that the
+* server would not process the request due to something the server considered
+* to be a client error. The reason for a 400 response is typically due to
+* malformed request syntax, invalid request message framing, or deceptive
+* request routing.
+*
+* Clients that receive a 400 response should expect that repeating the request
+* without modification will fail with the same error.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/400
+*/
+function badRequest(body) {
+	return response(400, body ?? "Bad request");
+}
+
+//#endregion
+//#region src/response/created.ts
+/**
+* 201 Created
+*
+* The HTTP 201 Created successful response status code indicates that the HTTP
+* request has led to the creation of a resource. This status code is commonly
+* sent as the result of a POST request.
+*
+* The new resource, or a description and link to the new resource, is created
+* before the response is returned. The newly-created items can be returned in
+* the body of the response message, but must be locatable by the URL of the
+* initiating request or by the URL in the value of the Location header provided
+* with the response.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/201
+*/
+function created(body) {
+	return response(201, body);
+}
+
+//#endregion
+//#region src/response/forbidden.ts
+/**
+* 403 Forbidden
+*
+* The HTTP 403 Forbidden client error response status code indicates that the
+* server understood the request but refused to process it. This status is
+* similar to 401, except that for 403 Forbidden responses, authenticating or
+* re-authenticating makes no difference. The request failure is tied to
+* application logic, such as insufficient permissions to a resource or action.
+*
+* Clients that receive a 403 response should expect that repeating the request
+* without modification will fail with the same error. Server owners may decide
+* to send a 404 response instead of a 403 if acknowledging the existence of a
+* resource to clients with insufficient privileges is not desired.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/403
+*/
+function forbidden(body) {
+	return response(403, body ?? "Forbidden");
+}
+
+//#endregion
+//#region src/response/found.ts
+/**
+* 302 Found
+*
+* The HTTP 302 Found redirection response status code indicates that the
+* requested resource has been temporarily moved to the URL in the Location
+* header.
+*
+* A browser receiving this status will automatically request the resource at
+* the URL in the Location header, redirecting the user to the new page. Search
+* engines receiving this response will not attribute links to the original URL
+* to the new resource, meaning no SEO value is transferred to the new URL.
+*
+* > Note: In the Fetch Standard, when a user agent receives a 302 in response
+* > to a POST request, it uses the GET method in the subsequent redirection
+* > request, as permitted by the HTTP specification. To avoid user agents
+* > modifying the request, use 307 Temporary Redirect instead, as altering the
+* > method after a 307 response is prohibited.
+*
+* > In cases where you want any request method to be changed to GET, use 303
+* > See Other. This is useful when you want to give a response to a PUT method
+* > that is not the uploaded resource but a confirmation message such as: "you
+* > successfully uploaded XYZ".
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/302
+*/
+function permRedirect(location) {
+	return transfer(308, location);
+}
+
+//#endregion
+//#region src/response/methodNotAllowed.ts
+/**
+* 405 Method Not Allowed
+*
+* The HTTP 405 Method Not Allowed client error response status code indicates
+* that the server knows the request method, but the target resource doesn't
+* support this method. The server must generate an Allow header in a 405
+* response with a list of methods that the target resource currently supports.
+*
+* Improper server-side permissions set on files or directories may cause a 405
+* response when the request would otherwise be expected to succeed.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/405
+*/
+function methodNotAllowed(body) {
+	return response(405, body ?? "Method not allowed");
+}
+
+//#endregion
+//#region src/response/movedPermanently.ts
+/**
+* 301 Moved Permanently
+*
+* The HTTP 301 Moved Permanently redirection response status code indicates
+* that the requested resource has been permanently moved to the URL in the
+* Location header.
+*
+* A browser receiving this status will automatically request the resource at
+* the URL in the Location header, redirecting the user to the new page. Search
+* engines receiving this response will attribute links to the original URL to
+* the redirected resource, passing the SEO ranking to the new URL.
+*
+* > Note: In the Fetch Standard, when a user agent receives a 301 in response
+* > to a POST request, it uses the GET method in the subsequent redirection
+* > request, as permitted by the HTTP specification. To avoid user agents
+* > modifying the request, use 308 Permanent Redirect instead, as altering the
+* > method after a 308 response is prohibited.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/301
+*/
+function permRedirect$1(location) {
+	return transfer(308, location);
+}
+
+//#endregion
+//#region src/response/notModified.ts
+/**
+* 304 Not Modified
+*
+* The HTTP 304 Not Modified redirection response status code indicates that
+* there is no need to retransmit the requested resources.
+*
+* This response code is sent when the request is a conditional GET or HEAD
+* request with an If-None-Match or an If-Modified-Since header and the
+* condition evaluates to 'false'. It confirms that the resource cached by the
+* client is still valid and that the server would have sent a 200 OK response
+* with the resource if the condition evaluated to 'true'. See HTTP caching for
+* more information.
+*
+* The response must not contain a body and must include the headers that would
+* have been sent in an equivalent 200 response, such as:
+*
+* - Cache-Control
+* - Content-Location
+* - Date
+* - ETag
+* - Expires
+* - Vary
+*
+* > Note: Many developer tools' network panels of browsers create extraneous
+* > requests leading to 304 responses, so that access to the local cache is
+* > visible to developers.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/304
+*/
+function notModified(location) {
+	return transfer(304, location);
+}
+
+//#endregion
+//#region src/response/permanentRedirect.ts
+/**
+* 308 Permanent Redirect
+*
+* The HTTP 308 Permanent Redirect redirection response status code indicates
+* that the requested resource has been permanently moved to the URL given by
+* the Location header.
+*
+* A browser receiving this status will automatically request the resource at
+* the URL in the Location header, redirecting the user to the new page. Search
+* engines receiving this response will attribute links to the original URL to
+* the redirected resource, passing the SEO ranking to the new URL.
+*
+* The request method and the body will not be modified by the client in the
+* redirected request. A 301 Moved Permanently requires the request method and
+* the body to remain unchanged when redirection is performed, but this is
+* incorrectly handled by older clients to use the GET method instead.
+*
+* > Note: Some Web applications may use the 308 Permanent Redirect in a
+* > non-standard way and for different purposes. For example, Google Drive uses
+* > a 308 Resume Incomplete response to indicate to the client when an
+* > unfinished upload has stalled. See Perform a resumable download on the
+* > Google Drive documentation for more information.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/308
+*/
+function permanentRedirect(location) {
+	return transfer(308, location);
+}
+
+//#endregion
+//#region src/response/serverError.ts
+/**
+* 500 Server Error
+*
+* The HTTP 500 Internal Server Error server error response status code
+* indicates that the server encountered an unexpected condition that prevented
+* it from fulfilling the request. This error is a generic "catch-all" response
+* to server issues, indicating that the server cannot find a more appropriate
+* 5XX error to respond with.
+*
+* If you're a visitor seeing 500 errors on a web page, these issues require
+* investigation by server owners or administrators. There are many possible
+* causes of 500 errors, including: improper server configuration, out-of-memory
+* (OOM) issues, unhandled exceptions, improper file permissions, or other
+* complex factors. Server administrators may proactively log occurrences of
+* server error responses, like the 500 status code, with details about the
+* initiating requests to improve the stability of a service in the future.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/500
+*/
+function serverError(body) {
+	return response(500, body ?? "Server error");
+}
+
+//#endregion
+//#region src/response/temporaryRedirect.ts
+/**
+* 307 Temporary Redirect
+*
+* The HTTP 307 Temporary Redirect redirection response status code indicates
+* that the resource requested has been temporarily moved to the URL in the
+* Location header.
+*
+* A browser receiving this status will automatically request the resource at
+* the URL in the Location header, redirecting the user to the new page. Search
+* engines receiving this response will not attribute links to the original URL
+* to the new resource, meaning no SEO value is transferred to the new URL.
+*
+* The method and the body of the original request are reused to perform the
+* redirected request. In the cases where you want the request method to be
+* changed to GET, use 303 See Other instead. This is useful when you want to
+* give an answer to a successful PUT request that is not the uploaded resource,
+* but a status monitor or confirmation message like "You have successfully
+* uploaded XYZ".
+*
+* The difference between 307 and 302 is that 307 guarantees that the client
+* will not change the request method and body when the redirected request is
+* made. With 302, older clients incorrectly changed the method to GET. 307 and
+* 302 responses are identical when the request method is GET.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/307
+*/
+function temporaryRedirect(location) {
+	return transfer(307, location);
+}
+
+//#endregion
+//#region src/response/unauthorized.ts
+/**
+* 401 Unauthorized
+*
+* The HTTP 401 Unauthorized client error response status code indicates that a
+* request was not successful because it lacks valid authentication credentials
+* for the requested resource. This status code is sent with an HTTP
+* WWW-Authenticate response header that contains information on the
+* authentication scheme the server expects the client to include to make the
+* request successfully.
+*
+* A 401 Unauthorized is similar to the 403 Forbidden response, except that a
+* 403 is returned when a request contains valid credentials, but the client
+* does not have permissions to perform a certain action.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/401
+*/
+function unauthorized(body) {
+	return response(401, body ?? "Unauthorized");
+}
+
+//#endregion
+//#region src/response/unprocessable.ts
+/**
+* 422 Unprocessable Content
+*
+* The HTTP 422 Unprocessable Content client error response status code
+* indicates that the server understood the content type of the request content,
+* and the syntax of the request content was correct, but it was unable to
+* process the contained instructions.
+*
+* Clients that receive a 422 response should expect that repeating the request
+* without modification will fail with the same error.
+*
+* See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/422
+*/
+function unprocessable(body) {
+	return response(422, body ?? "Unprocessable");
+}
+
+//#endregion
+export { badRequest, created, forbidden, methodNotAllowed, notModified, permRedirect$1 as permRedirect, permRedirect as permRedirect$1, permanentRedirect, serverError, temporaryRedirect, unauthorized, unprocessable };
+//# sourceMappingURL=response-D-XpIuMH.js.map

package/dist/response-D-XpIuMH.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"response-D-XpIuMH.js","names":["permRedirect"],"sources":["../src/response/badRequest.ts","../src/response/created.ts","../src/response/forbidden.ts","../src/response/found.ts","../src/response/methodNotAllowed.ts","../src/response/movedPermanently.ts","../src/response/notModified.ts","../src/response/permanentRedirect.ts","../src/response/serverError.ts","../src/response/temporaryRedirect.ts","../src/response/unauthorized.ts","../src/response/unprocessable.ts"],"sourcesContent":["import response from \"./response\";\n\n/**\n * 400 Bad Request\n *\n * The HTTP 400 Bad Request client error response status code indicates that the\n * server would not process the request due to something the server considered\n * to be a client error. The reason for a 400 response is typically due to\n * malformed request syntax, invalid request message framing, or deceptive\n * request routing.\n *\n * Clients that receive a 400 response should expect that repeating the request\n * without modification will fail with the same error.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/400\n */\nexport default function badRequest(body?: object | string): Response {\n\treturn response(400, body ?? \"Bad request\");\n}\n","import response from \"./response\";\n\n/**\n * 201 Created\n *\n * The HTTP 201 Created successful response status code indicates that the HTTP\n * request has led to the creation of a resource. This status code is commonly\n * sent as the result of a POST request.\n *\n * The new resource, or a description and link to the new resource, is created\n * before the response is returned. The newly-created items can be returned in\n * the body of the response message, but must be locatable by the URL of the\n * initiating request or by the URL in the value of the Location header provided\n * with the response.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/201\n */\nexport default function created(body?: object | string): Response {\n\treturn response(201, body);\n}\n","import response from \"./response\";\n\n/**\n * 403 Forbidden\n *\n * The HTTP 403 Forbidden client error response status code indicates that the\n * server understood the request but refused to process it. This status is\n * similar to 401, except that for 403 Forbidden responses, authenticating or\n * re-authenticating makes no difference. The request failure is tied to\n * application logic, such as insufficient permissions to a resource or action.\n *\n * Clients that receive a 403 response should expect that repeating the request\n * without modification will fail with the same error. Server owners may decide\n * to send a 404 response instead of a 403 if acknowledging the existence of a\n * resource to clients with insufficient privileges is not desired.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/403\n */\nexport default function forbidden(body?: object | string): Response {\n\treturn response(403, body ?? \"Forbidden\");\n}\n","import transfer from \"./transfer\";\n\n/**\n * 302 Found\n *\n * The HTTP 302 Found redirection response status code indicates that the\n * requested resource has been temporarily moved to the URL in the Location\n * header.\n *\n * A browser receiving this status will automatically request the resource at\n * the URL in the Location header, redirecting the user to the new page. Search\n * engines receiving this response will not attribute links to the original URL\n * to the new resource, meaning no SEO value is transferred to the new URL.\n *\n * > Note: In the Fetch Standard, when a user agent receives a 302 in response\n * > to a POST request, it uses the GET method in the subsequent redirection\n * > request, as permitted by the HTTP specification. To avoid user agents\n * > modifying the request, use 307 Temporary Redirect instead, as altering the\n * > method after a 307 response is prohibited.\n *\n * > In cases where you want any request method to be changed to GET, use 303\n * > See Other. This is useful when you want to give a response to a PUT method\n * > that is not the uploaded resource but a confirmation message such as: \"you\n * > successfully uploaded XYZ\".\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/302\n */\nexport default function permRedirect(location: string): Response {\n\treturn transfer(308, location);\n}\n","import response from \"./response\";\n\n/**\n * 405 Method Not Allowed\n *\n * The HTTP 405 Method Not Allowed client error response status code indicates\n * that the server knows the request method, but the target resource doesn't\n * support this method. The server must generate an Allow header in a 405\n * response with a list of methods that the target resource currently supports.\n *\n * Improper server-side permissions set on files or directories may cause a 405\n * response when the request would otherwise be expected to succeed.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/405\n */\nexport default function methodNotAllowed(body?: object | string): Response {\n\treturn response(405, body ?? \"Method not allowed\");\n}\n","import transfer from \"./transfer\";\n\n/**\n * 301 Moved Permanently\n *\n * The HTTP 301 Moved Permanently redirection response status code indicates\n * that the requested resource has been permanently moved to the URL in the\n * Location header.\n *\n * A browser receiving this status will automatically request the resource at\n * the URL in the Location header, redirecting the user to the new page. Search\n * engines receiving this response will attribute links to the original URL to\n * the redirected resource, passing the SEO ranking to the new URL.\n *\n * > Note: In the Fetch Standard, when a user agent receives a 301 in response\n * > to a POST request, it uses the GET method in the subsequent redirection\n * > request, as permitted by the HTTP specification. To avoid user agents\n * > modifying the request, use 308 Permanent Redirect instead, as altering the\n * > method after a 308 response is prohibited.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/301\n */\nexport default function permRedirect(location: string): Response {\n\treturn transfer(308, location);\n}\n","import transfer from \"./transfer\";\n\n/**\n * 304 Not Modified\n *\n * The HTTP 304 Not Modified redirection response status code indicates that\n * there is no need to retransmit the requested resources.\n *\n * This response code is sent when the request is a conditional GET or HEAD\n * request with an If-None-Match or an If-Modified-Since header and the\n * condition evaluates to 'false'. It confirms that the resource cached by the\n * client is still valid and that the server would have sent a 200 OK response\n * with the resource if the condition evaluated to 'true'. See HTTP caching for\n * more information.\n *\n * The response must not contain a body and must include the headers that would\n * have been sent in an equivalent 200 response, such as:\n *\n * - Cache-Control\n * - Content-Location\n * - Date\n * - ETag\n * - Expires\n * - Vary\n *\n * > Note: Many developer tools' network panels of browsers create extraneous\n * > requests leading to 304 responses, so that access to the local cache is\n * > visible to developers.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/304\n */\nexport default function notModified(location: string): Response {\n\treturn transfer(304, location);\n}\n","import transfer from \"./transfer\";\n\n/**\n * 308 Permanent Redirect\n *\n * The HTTP 308 Permanent Redirect redirection response status code indicates\n * that the requested resource has been permanently moved to the URL given by\n * the Location header.\n *\n * A browser receiving this status will automatically request the resource at\n * the URL in the Location header, redirecting the user to the new page. Search\n * engines receiving this response will attribute links to the original URL to\n * the redirected resource, passing the SEO ranking to the new URL.\n *\n * The request method and the body will not be modified by the client in the\n * redirected request. A 301 Moved Permanently requires the request method and\n * the body to remain unchanged when redirection is performed, but this is\n * incorrectly handled by older clients to use the GET method instead.\n *\n * > Note: Some Web applications may use the 308 Permanent Redirect in a\n * > non-standard way and for different purposes. For example, Google Drive uses\n * > a 308 Resume Incomplete response to indicate to the client when an\n * > unfinished upload has stalled. See Perform a resumable download on the\n * > Google Drive documentation for more information.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/308\n */\nexport default function permanentRedirect(location: string): Response {\n\treturn transfer(308, location);\n}\n","import response from \"./response\";\n\n/**\n * 500 Server Error\n *\n * The HTTP 500 Internal Server Error server error response status code\n * indicates that the server encountered an unexpected condition that prevented\n * it from fulfilling the request. This error is a generic \"catch-all\" response\n * to server issues, indicating that the server cannot find a more appropriate\n * 5XX error to respond with.\n *\n * If you're a visitor seeing 500 errors on a web page, these issues require\n * investigation by server owners or administrators. There are many possible\n * causes of 500 errors, including: improper server configuration, out-of-memory\n * (OOM) issues, unhandled exceptions, improper file permissions, or other\n * complex factors. Server administrators may proactively log occurrences of\n * server error responses, like the 500 status code, with details about the\n * initiating requests to improve the stability of a service in the future.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/500\n */\nexport default function serverError(body?: object | string): Response {\n\treturn response(500, body ?? \"Server error\");\n}\n","import transfer from \"./transfer\";\n\n/**\n * 307 Temporary Redirect\n *\n * The HTTP 307 Temporary Redirect redirection response status code indicates\n * that the resource requested has been temporarily moved to the URL in the\n * Location header.\n *\n * A browser receiving this status will automatically request the resource at\n * the URL in the Location header, redirecting the user to the new page. Search\n * engines receiving this response will not attribute links to the original URL\n * to the new resource, meaning no SEO value is transferred to the new URL.\n *\n * The method and the body of the original request are reused to perform the\n * redirected request. In the cases where you want the request method to be\n * changed to GET, use 303 See Other instead. This is useful when you want to\n * give an answer to a successful PUT request that is not the uploaded resource,\n * but a status monitor or confirmation message like \"You have successfully\n * uploaded XYZ\".\n *\n * The difference between 307 and 302 is that 307 guarantees that the client\n * will not change the request method and body when the redirected request is\n * made. With 302, older clients incorrectly changed the method to GET. 307 and\n * 302 responses are identical when the request method is GET.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/307\n */\nexport default function temporaryRedirect(location: string): Response {\n\treturn transfer(307, location);\n}\n","import response from \"./response\";\n\n/**\n * 401 Unauthorized\n *\n * The HTTP 401 Unauthorized client error response status code indicates that a\n * request was not successful because it lacks valid authentication credentials\n * for the requested resource. This status code is sent with an HTTP\n * WWW-Authenticate response header that contains information on the\n * authentication scheme the server expects the client to include to make the\n * request successfully.\n *\n * A 401 Unauthorized is similar to the 403 Forbidden response, except that a\n * 403 is returned when a request contains valid credentials, but the client\n * does not have permissions to perform a certain action.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/401\n */\nexport default function unauthorized(body?: object | string): Response {\n\treturn response(401, body ?? \"Unauthorized\");\n}\n","import response from \"./response\";\n\n/**\n * 422 Unprocessable Content\n *\n * The HTTP 422 Unprocessable Content client error response status code\n * indicates that the server understood the content type of the request content,\n * and the syntax of the request content was correct, but it was unable to\n * process the contained instructions.\n *\n * Clients that receive a 422 response should expect that repeating the request\n * without modification will fail with the same error.\n *\n * See https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/422\n */\nexport default function unprocessable(body?: object | string): Response {\n\treturn response(422, body ?? \"Unprocessable\");\n}\n"],"mappings":";;;;;;;;;;;;;;;;;AAgBA,SAAwB,WAAW,MAAkC;AACpE,QAAO,SAAS,KAAK,QAAQ,cAAc;;;;;;;;;;;;;;;;;;;;ACA5C,SAAwB,QAAQ,MAAkC;AACjE,QAAO,SAAS,KAAK,KAAK;;;;;;;;;;;;;;;;;;;;;ACA3B,SAAwB,UAAU,MAAkC;AACnE,QAAO,SAAS,KAAK,QAAQ,YAAY;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;ACQ1C,SAAwB,aAAa,UAA4B;AAChE,QAAO,SAAS,KAAK,SAAS;;;;;;;;;;;;;;;;;;ACb/B,SAAwB,iBAAiB,MAAkC;AAC1E,QAAO,SAAS,KAAK,QAAQ,qBAAqB;;;;;;;;;;;;;;;;;;;;;;;;;ACMnD,SAAwBA,eAAa,UAA4B;AAChE,QAAO,SAAS,KAAK,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;ACQ/B,SAAwB,YAAY,UAA4B;AAC/D,QAAO,SAAS,KAAK,SAAS;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;ACL/B,SAAwB,kBAAkB,UAA4B;AACrE,QAAO,SAAS,KAAK,SAAS;;;;;;;;;;;;;;;;;;;;;;;;ACP/B,SAAwB,YAAY,MAAkC;AACrE,QAAO,SAAS,KAAK,QAAQ,eAAe;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;ACM7C,SAAwB,kBAAkB,UAA4B;AACrE,QAAO,SAAS,KAAK,SAAS;;;;;;;;;;;;;;;;;;;;;ACX/B,SAAwB,aAAa,MAAkC;AACtE,QAAO,SAAS,KAAK,QAAQ,eAAe;;;;;;;;;;;;;;;;;;ACJ7C,SAAwB,cAAc,MAAkC;AACvE,QAAO,SAAS,KAAK,QAAQ,gBAAgB"}