shakshuka
05/06/2023, 6:28 PMRealJim
05/07/2023, 10:22 AMexport default defineConfig({
plugins: [sveltekit(),wasm(),topLevelAwait()],
build: {
rollupOptions: {plugins: [wasm(),topLevelAwait()],},
},
}
and the +page.server.js
import { OpenAI } from "langchain/llms/openai";
export async function load() {
const model = new OpenAI();
const res = await model.call("hello");
return res;
}
what may be the problem?Pasukaru
05/07/2023, 1:20 PMd46bcbfb96be0041b72c7b1fc72a076f
Pages.dev: https://6509bcfe.nip-5.pages.dev/
Deployment Id: 6509bcfe-10f3-48a6-b6b4-1e92859922d0
shuyz
05/07/2023, 3:39 PMMuhymin
05/07/2023, 4:11 PMConnect Timeout Error
a lot. First, it was one image. But now the more images are getting added to the CMS, the more we are getting Connect Timeout Error
. Why is it happening? Is there any concurrent request limit in Cloudflare Pages? And if there's a limit, should Cloudflare automatically handle this?nish
05/07/2023, 11:55 PMnicolasfry
05/08/2023, 2:02 AM21:46:22.183 AGsuccess Building production JavaScript and CSS bundles - 189.929s
21:46:22.183
21:46:22.209 AGGatsby Config Mode: production
21:46:22.210
21:46:42.421 /opt/build/bin/build: line 39: 1605 Segmentation fault gatsby build
21:46:42.483 Failed: build command exited with code: 139
21:46:43.736 Failed: error occurred while running build command
Matt Grah.am
05/08/2023, 3:32 AMmarkoan
05/09/2023, 12:49 AMSmallShen
05/09/2023, 3:26 AMexample.com/api/*
, example.com
is hosted on pages. If I directly visit the api routes, it invoke the worker, but when I try to fetch /api/*
endpoints in the page function, it will try to fetch from pages not workers. How do I solve this issue?Msh
05/09/2023, 7:55 AMMuhymin
05/09/2023, 11:22 AMnode_modules
folder so that consequents build run faster. I see the message Started restoring cached node modules
and Finished restoring cached node modules
messages on the top of all the deployment logs. But it's not working actually.
npm
used to reinstall and download all the dependencies every time. Now, I am using pnpm
, and the pnpm store is set to node_modules/.pnpm-store
but it's redownloading and installing all the dependencies every time.
I am also using astro-imagetools
which stores its cache inside node_modules/.cache/astro-imagetools
which is also not working. And it's heavily impacting the build time.
I have tested both retrying deployments, adding a new commit, and triggering the deploy hooks. But none of them is able to restore the node_modules
.new2discord
05/09/2023, 12:36 PMhttps://cdn.discordapp.com/attachments/1105473308436201493/1105473309363150889/image.png▾
mapple
05/10/2023, 6:49 AMcog25
05/10/2023, 1:53 PMTetraEtc
05/11/2023, 11:25 AMhttps://cdn.discordapp.com/attachments/1106180202708602911/1106180203207741511/image.png▾
https://cdn.discordapp.com/attachments/1106180202708602911/1106180203522306148/image.png▾
BryceWray
05/11/2023, 1:08 PM_middleware.js
stuff for the first time with CF Pages, in an attempt to use it instead of an existing CF Worker. The middleware works perfectly on the pages.dev
version — but, on the custom-domain version from that pages.dev
, only the HTML files are affected even though it’s for all routes and files. To be more specific: on the pages.dev
version, a number of custom headers (such as for caching) are added to a variety of file types, including CSS and image files; but, on the custom-domain version, this works for only the HTML files.
Is there something special I have to do in the domain’s DNS, or elsewhere, to make the middleware work properly on the custom domain, too? (And I did remove the custom domain’s routes from the Worker for the test, so the Worker shouldn’t have been interfering.)
The pages.dev
domain = static-site-2to.pages.dev
The custom domain = brycewray.com
**Note**: I have had to re-add the custom domain routes to the Worker and take the _middleware.js
file out of the project in order to regain the previous functionality, at least until I can learn why the middleware file doesn’t work on the custom domain. Let me know if you want me to restore the test setup.alexanderniebuhr
05/11/2023, 7:18 PMpages-action
or wrangler-action
doe always lead to failed deployments.
However using the cli works.
pnpx wrangler pages publish apps/blog/dist --project-name=test
* Anyone an Idea?*
https://cdn.discordapp.com/attachments/1106299318744387715/1106299319029616690/Screenshot_2023-05-11_at_21.16.41.png▾
https://cdn.discordapp.com/attachments/1106299318744387715/1106299319553888256/Screenshot_2023-05-11_at_21.17.28.png▾
bjornftw
05/11/2023, 7:35 PMNODE_VERSION
environment set to 16.15.0
. After deployment I see a npm ERR! Incorrect or missing password.
error. I added my NPM token as NPM_TOKEN
but not working. What to do
https://cdn.discordapp.com/attachments/1106303463383638158/1106303463626903642/Screenshot_2023-05-11_at_21.34.11.png▾
kevinflo
05/11/2023, 11:05 PMbigbhoooi
05/12/2023, 4:56 AMbrettr91
05/12/2023, 7:31 AMchrisgan
05/12/2023, 2:04 PMhttps://cdn.discordapp.com/attachments/1106582730680045679/1106582730994626580/chrome_XCSfh1CjkU.png▾
https://cdn.discordapp.com/attachments/1106582730680045679/1106582731334361130/msedge_Mr8eHsqWrC.png▾
https://cdn.discordapp.com/attachments/1106582730680045679/1106582731854450759/chrome_7W3BGOztnz.png▾
DanTheGoodman
05/12/2023, 10:13 PMhttps://cdn.discordapp.com/attachments/1106705849298190446/1106705849415647365/image.png▾
ScarabCoder
05/12/2023, 11:29 PMJanno
05/13/2023, 6:21 AMRial
05/13/2023, 10:51 AMPedrex
05/13/2023, 12:20 PMnarra
05/13/2023, 2:15 PMnpm install -g pnpm && pnpm i && pnpm build
My environment is also using the following node version : NODE_VERSION 18.14.0
TehZombiJesus
05/14/2023, 1:44 PMnoximityweb.pages.dev
Account ID: b068e1072ce66279dd2a98699d3ab816
Log:
Cloning repository...
From https://github.com/NoximityMC/NoximityWeb
* branch dba2ef8dd157da87b84d1d49ddc3537705c57d4d -> FETCH_HEAD
HEAD is now at dba2ef8 Initial commit
Success: Finished cloning repository files
Installing nodejs 18.16.0
nodejs 18.16.0 is already installed
Installing project dependencies: npm clean-install --progress=false
added 364 packages, and audited 365 packages in 6s
41 packages are looking for funding
run `npm fund` for details
08:55:50.261
08:55:50.261 found 0 vulnerabilities
Executing user command: npm run build
> base@0.0.0 build
> tsc && vite build
vite v4.3.5 building for production...
transforming...
✓ 25 modules transformed.
✓ built in 750ms
Could not resolve "../style/Navbar.scss" from "src/components/Navbar.tsx"
file: /opt/buildhome/repo/src/components/Navbar.tsx
error during build:
RollupError: Could not resolve "../style/Navbar.scss" from "src/components/Navbar.tsx"
at error (file:///opt/buildhome/repo/node_modules/rollup/dist/es/shared/node-entry.js:2125:30)
at ModuleLoader.handleInvalidResolvedId (file:///opt/buildhome/repo/node_modules/rollup/dist/es/shared/node-entry.js:23938:24)
at file:///opt/buildhome/repo/node_modules/rollup/dist/es/shared/node-entry.js:23900:26
Failed: Error while executing user command. Exited with error code: 1
Failed: build command exited with code: 1
Failed: error occurred while running build command