yeah. I might even go for a non serverless solution. Seems serverless is really expensive for this u
yeah. I might even go for a non serverless solution. Seems serverless is really expensive for this use case.
--local)
any type, and see if it works.any type to the catch block like so, and see if it stops throwing that error.
* and then another ! rule following to just remove on that one path/* match /hello/whoami?const resp = await fetch(`...`, {
cf: {
cacheTtl: 60 * 10,
},
});catch (error) {
console.error(`Error while inserting row into accesslog table: ${error}`);
return Response.json({ message: `Error while inserting row into accesslog table: ${error.message}` });
}try {
// ...
} catch (error: any) {
console.error(`Error while inserting row into accesslog table: ${error}`);
return Response.json({ message: `Error while inserting row into accesslog table: ${error.message}` });
}try {
await env.DB.prepare(
"INSERT INTO accesslog (ip, time, path) VALUES (?1, ?2, ?3)"
).bind(ip, time, pathname).run();
} catch (error) {
console.error(`Error while inserting row into accesslog table: ${error}`);
return Response.json({ message: `Error while inserting row into accesslog table: ${error.message}` });
}
}try {
await env.DB.prepare(
"INSERT INTO accesslog (ip, time, path) VALUES (?1, ?2, ?3)"
).bind(ip, time, pathname).run();
} catch (error: any) {
console.error(`Error while inserting row into accesslog table: ${error}`);
return Response.json({ message: `Error while inserting row into accesslog table: ${error.message}` });
}
} node_modules/clean-css/lib/options/format.js:1:30: ERROR: Could not resolve "os"
node_modules/clean-css/lib/options/inline-request.js:1:18: ERROR: Could not resolve "url"
node_modules/clean-css/lib/options/rebase-to.js:1:19: ERROR: Could not resolve "path"
node_modules/clean-css/lib/reader/apply-source-maps.js:1:17: ERROR: Could not resolve "fs"
node_modules/clean-css/lib/reader/apply-source-maps.js:2:19: ERROR: Could not resolve "path"/hello/whoami