Deploying on Cloudflare Pages

[Strongeyed]

Hi team,

Nearly there to deploy on Cloudflare Pages, however getting the following error:

15:31:33.784	> nuxt build
15:31:33.784
15:32:16.414	Finished
15:32:16.415	Note: No functions dir at /functions found. Skipping.
15:32:16.415	Validating asset output directory
15:32:16.415	Error: Output directory "dist" not found.
15:32:17.430	Failed: build output directory not found

Actions taken:

• Added to the ENV public key, store id and URL.
• Tried NPM RUN BUILD
• Added Node ENV production node npm build && next export

Can someone maybe give some input on how they have configured their build on CF pages?
 

[logeshswell]

@Strongeyed If it refers to the origin theme, then the build command should be,
yarn run build
and the definition should be,
yarn sync && nuxt build && nuxt generate

Reason:
nuxt generate command generates dist directory and the error occurs since it is missing.

[logeshswell]

@Strongeyed Can you confirm if this fix is merged into your private repo through which Cloudflare is deployed?

[logeshswell]

If the fix is applied, then please follow the below next steps:

1. Delete the swell-hosted storefront: https://synthesizer-new-zealand.swell.store/admin/storefronts/vGfMtsXq
2. You can edit the theme using the storefront editor: https://synthesizer-new-zealand.swell.store/admin/storefronts/2eGwGn1Z/editor
3. Whenever the theme is edited, you should redeploy your Cloudflare production build.

[logeshswell]

I have tried this a couple of times but nothing seems to happen

Can you share the latest deployment logs?

[Strongeyed]

@logeshswell Deploying the fix as we speak, fingers crossed it will work, otherwise I will share the deployment logs with you, no problem!
Will also follow the above steps:

If the fix is applied, then please follow the below next steps:

Delete the swell-hosted storefront: https://synthesizer-new-zealand.swell.store/admin/storefronts/vGfMtsXq
You can edit the theme using the storefront editor: https://synthesizer-new->zealand.swell.store/admin/storefronts/2eGwGn1Z/editor
Whenever the theme is edited, you should redeploy your Cloudflare production build.

[Strongeyed]

@logeshswell We are all good I think, all changes were deployed and I have implemented the fix. Thank you so much for your time!

[Strongeyed]

Hi @logeshswell I have an issue deploying once again on Cloudflare. I did not make any changes to the build plan or my own hosted repo, so wondering why this happens?

11:00:14.350	- [bridge] Nuxt bridge is required
11:00:15.823
11:00:15.824	ERROR Could not resolve routes
11:00:15.824
11:00:15.824
11:00:15.825	FATAL Cannot destructure property 'results' of 'initialFetch' as it is null.
11:00:15.825
11:00:15.825	at paginateThrough (modules/swell/utils/getRoutes.js:66:11)
11:00:15.825	at runMicrotasks ()
11:00:15.825	at processTicksAndRejections (node:internal/process/task_queues:96:5)
11:00:15.826	at async getRoutes (modules/swell/utils/getRoutes.js:9:3)
11:00:15.826	at async Generator.initRoutes (node_modules/@nuxt/generator/dist/generator.js:131:26)
11:00:15.826	at async Generator.generate (node_modules/@nuxt/generator/dist/generator.js:74:20)
11:00:15.826	at async generate$1 (node_modules/@nuxt/cli/dist/cli-generate.js:46:22)
11:00:15.826	at async Object.run (node_modules/@nuxt/cli/dist/cli-generate.js:284:7)
11:00:15.826	at async NuxtCommand.run (node_modules/@nuxt/cli/dist/cli-index.js:413:7)
11:00:15.827
11:00:15.829
11:00:15.830	╭──────────────────────────────────────────────────────────────────────────────╮│ ││ ✖ Nuxt Fatal Error ││ ││ TypeError: Cannot destructure property 'results' of 'initialFetch' as it ││ is ││ null. ││ │╰──────────────────────────────────────────────────────────────────────────────╯
11:00:15.830
11:00:15.874	Failed: build command exited with code: 1
11:00:16.822	Failed: error occurred while running build command

[Strongeyed]

@logeshswell On one of my other stores I forked the swell origin theme repo directly (it's the latest version) but I get this when I try and deploy it with the same settings on Cloudflare, any ideas?:

08:33:26.220	➤ YN0002: │ nuxt@npm:2.15.8 doesn't provide consola (p2d844), requested by @nuxt/components
08:33:26.220	➤ YN0060: │ swell-origin-theme@workspace:. provides eslint (p44ffd) with version 8.16.0, which doesn't satisfy what @nuxtjs/eslint-config and some of its descendants request
08:33:26.220	➤ YN0060: │ swell-origin-theme@workspace:. provides stylelint (pd70aa) with version 15.6.2, which doesn't satisfy what stylelint-config-prettier requests
08:33:26.220	➤ YN0060: │ swell-origin-theme@workspace:. provides stylelint (p8d06d) with version 15.6.2, which doesn't satisfy what stylelint-config-recommended-vue and some of its descendants request
08:33:26.220	➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements for details, where is the six-letter p-prefixed code
08:33:26.225	➤ YN0000: └ Completed in 14s 107ms
08:33:26.347	➤ YN0000: ┌ Post-resolution validation
08:33:26.347	➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
08:33:26.347	➤ YN0000: └ Completed
08:33:26.348	➤ YN0000: Failed with errors in 14s 235ms
08:33:26.418	Error: Exit with error code: 1
08:33:26.418	at ChildProcess. (/snapshot/dist/run-build.js)
08:33:26.419	at Object.onceWrapper (node:events:652:26)
08:33:26.419	at ChildProcess.emit (node:events:537:28)
08:33:26.420	at ChildProcess._handle.onexit (node:internal/child_process:291:12)
08:33:26.427	Failed: build command exited with code: 1
08:33:27.336	Failed: error occurred while running build command

[logeshswell]

@Strongeyed I got to know that your Cloudflare deployment is successful now after updating the build directory to /dist.
Can you please confirm the same?

[Strongeyed]

@Strongeyed This error may come when you use the incorrect credentials from a different storefront but in the same swell store.

1. Can you check whether you use credentials from this page?

2. Do you receive the same error on your local machine?

Because, I tried yarn run build in my local machine with your swell store and didn't encounter any issues while following the same credentials mentioned on the page.

Hi Logesh,

Yes thank you for your support, I just wanted to ask if you could have a look at my other store as well which I’ll deploy with the same settings, the store ID is ‘your-store’

[logeshswell]

@Strongeyed Yes sure, if you encounter any issues, just drop a text here (or) to the support team with the screen recordings like previously. I can assist you at the earliest.

But, please don't post it in both places as we get confused with your inputs sometimes.

[Strongeyed]

@logeshswell Sure, I completely understand. I will reach out through one channel at a time to avoid confusion. I do think at this moment I can manage the deployment of the other store, if I need you I will sing out!