Error: Cannot find module '@vercel\commerce-local\next.config' #681

radgezito · 2022-02-12T20:00:46Z

After cloning the project, creating the .env.local file to use @vercel/commerce-local I get an error message when I run yarn dev command

$ yarn dev
yarn run v1.22.10
$ next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info - Loaded env from c:\test\commerce\site.env.local
error - Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error
Error: Cannot find module '@vercel\commerce-local\next.config'
Require stack:

c:\test\commerce\site\noop.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.mod._resolveFilename (c:\test\commerce\node_modules\next\dist\build\webpack\require-hook.js:179:28)
at resolveFileName (c:\test\commerce\node_modules\resolve-from\index.js:29:39)
at resolveFrom (c:\test\commerce\node_modules\resolve-from\index.js:43:9)
at module.exports (c:\test\commerce\node_modules\resolve-from\index.js:46:47)
at module.exports (c:\test\commerce\node_modules\import-from\index.js:4:55)
at module.exports (c:\test\commerce\node_modules\import-cwd\index.js:4:30)
at Object.withCommerceConfig (c:\test\commerce\packages\commerce\dist\config.cjs:19:30)
at withCommerceConfig (c:\test\commerce\site\commerce-config.js:102:15)
at Object. (c:\test\commerce\site\next.config.js:11:18) {
code: 'MODULE_NOT_FOUND',
requireStack: [ 'C:\temp\delete\commerce\site\noop.js' ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

amir-zahedi · 2022-02-13T00:48:36Z

After cloning the project, creating the .env.local file to use @vercel/commerce-local I get an error message when I run yarn dev command

$ yarn dev yarn run v1.22.10 $ next dev ready - started server on 0.0.0.0:3000, url: http://localhost:3000 info - Loaded env from c:\test\commerce\site.env.local error - Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error Error: Cannot find module '@vercel\commerce-local\next.config' Require stack:

c:\test\commerce\site\noop.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.mod._resolveFilename (c:\test\commerce\node_modules\next\dist\build\webpack\require-hook.js:179:28)
at resolveFileName (c:\test\commerce\node_modules\resolve-from\index.js:29:39)
at resolveFrom (c:\test\commerce\node_modules\resolve-from\index.js:43:9)
at module.exports (c:\test\commerce\node_modules\resolve-from\index.js:46:47)
at module.exports (c:\test\commerce\node_modules\import-from\index.js:4:55)
at module.exports (c:\test\commerce\node_modules\import-cwd\index.js:4:30)
at Object.withCommerceConfig (c:\test\commerce\packages\commerce\dist\config.cjs:19:30)
at withCommerceConfig (c:\test\commerce\site\commerce-config.js:102:15)
at Object. (c:\test\commerce\site\next.config.js:11:18) {
code: 'MODULE_NOT_FOUND',
requireStack: [ 'C:\temp\delete\commerce\site\noop.js' ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Following this solved my issue @radgezito
#664

Qwertin · 2022-02-13T18:45:04Z

same problem, but with '@vercel\commerce-spree\next.config'

Dev05-Telnet · 2022-02-15T07:43:54Z

I too have the same problem while running in windows.
but it works well in Ubuntu

MiguelMinoldo · 2022-02-15T14:33:36Z

Same here, getting the very same issue.. any update on this?

aubryll · 2022-02-16T17:40:38Z

This is a quick hack and not a fix

I am using spree as my provider. To get past this issue I ended up modifying the \packages\commerce\src\config.cjs this way

      const path = require('path')
      const merge = require('deepmerge')
      const importCwd = require('import-cwd')

      function withCommerceConfig(nextConfig = {}) {
        const commerce = nextConfig.commerce || {}
        const { provider } = commerce
        const newProvider = provider.split('-')[1];
      
        if (!newProvider) {
          throw new Error(
            `The commerce provider is missing, please add a valid provider name`
          )
        }
      
        process.chdir("../");
        process.chdir("./packages")
        const commerceNextConfig = importCwd(path.join(process.cwd(),newProvider,'src', 'next.config.cjs'));
        const config = merge(nextConfig, commerceNextConfig)
        process.chdir("../");
        process.chdir("./site");
        
        config.env = config.env || {}
      
        Object.entries(config.commerce.features).forEach(([k, v]) => {
          if (v) config.env[`COMMERCE_${k.toUpperCase()}_ENABLED`] = true
        })
      
        return config
      }
      
      module.exports = { withCommerceConfig }

Code breakdown
I am not sure how the developers missed this but when you set the provider to @vercel/commerce-spree the app will try to look for a folder in packages by the name of @vercel/commerce-spree if you set your provider to spree it will complain that this is not a valid provider.

To benefit both worlds we get the last part after the last dash from the provider name with this line const newProvider = provider.split('-')[1];
From my personal experience, it uses ./site as its working directory, this makes it impossible for importCwd to find the next.config.cjs so you need to change directories using process.chdir
The last part is it tries to import next.config.js instead of next.config.cjs so we rename the import to next.config.cjs or rename the file to next.config.js
Then I ran yarn turbo run build this part did not succeed but it managed to set the right variables
And finally, I navigated to ./site and ran yarn dev and it worked.

HeavenlyEntity · 2022-02-19T05:31:54Z

Hey @radgezito @Qwertin the best thing to do is just checkout branch bump and fork that. Fixed the all issues for me. I think this will be the best option until the devs fix up the core issue on. #515

gregonarash · 2022-02-20T03:31:58Z

@radgezito @Qwertin

I hope this might help. I was able to run localhost no problem, just with yarn dev in the main monorepo folder (not in /site) , it starts localhost:3000 just fine.

Where I wasted a day was getting preview deployments on git push. The builds would fail with:

"error - failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error"

What made it work is overriding the Build Command in Build & Development Settings to cd .. && yarn build

sarathjasrin · 2022-02-21T20:39:10Z

I'm facing the same issue. I couldn't run it in the local.

Varagos · 2022-02-21T21:07:58Z

Also facing this problem

sarathjasrin · 2022-02-22T05:50:43Z

Also facing this problem

#681 (comment)

Helped me to fix it for now.

timothyk0908 · 2022-03-01T11:19:24Z

Also facing the same issue, Windows 10 fresh clone

lukasmiller · 2022-03-01T21:04:31Z

I ran into this issue as well, on a fresh clone on a Windows 11 machine this is how I fixed it:

Created .env.local and modified per my backend (vendure)
Ran the following build commands from the /site directory:
yarn
yarn workspace @vercel/commerce build
yarn workspace @vercel/commerce-local build
yarn workspace @vercel/commerce-vendure build

And finally made changes to the config.cjs file as outlined in #681 (comment)

After doing this on a fresh clone I was able to get it running without error using yarn next dev -p 8000.

CristianCucunuba · 2022-03-03T18:23:49Z

@aubryll Running yarn dev in the main folder instead of running it inside the /site folder in the installation process fixed the issue for me , maybe the docs are outdated after including turborepo

OnlyC · 2022-03-16T20:30:05Z

@CristianCucunuba running yarn dev in the main folder still give me this error

CrisleyAlves · 2022-03-25T22:10:31Z

#681 (comment)

It worked for me too. Thank you.

GarlandM · 2022-03-29T09:34:57Z

+1 to this issue, hoping it gets fixed instead of having to rely on the workaround.

Shaffan · 2022-03-29T16:00:07Z

Trying to run this on a Windows 10 machine with the local provider and I'm running into the same issue.

I noticed that it's making changes to my tsconfig whenever I build:

Using #681 (comment) as a temp workaround 🙏🏻

dominiksipowicz · 2022-04-13T15:28:56Z

Thi issue should be fixed now by #728

ashishkpaul · 2022-05-16T11:41:56Z

What help me, I run the command yarn in a ./packages/"api_backend_provider" then run the command yarn dev in site directory

aubryll · 2022-05-16T11:54:50Z

What help me, I run the command yarn in a ./packages/"api_backend_provider" then run the command yarn dev in site directory

@ashishkpaul run yarn dev in the root directory.

ashishkpaul · 2022-05-16T11:57:35Z

sir might be its not compiling in a root directory. its done within a 49ms
yarn run v1.22.18
$ turbo run dev
Done in 0.49s

ashishkpaul · 2022-05-16T12:13:01Z

What help me, I run the command yarn in a ./packages/"api_backend_provider" then run the command yarn dev in site directory

@ashishkpaul run yarn dev in the root directory.

sir i am using spree 4.4 , can you guide me on these errors by running the command yarn dev

next-commerce:dev: event - compiled client and server successfully in 5s (889 modules)
next-commerce:dev: getAllProducts called. Configuration:  getAllProductsVariables:  { first: 6 } config:  { locale: 'en-US', locales: [ 'en-US', 'es' ] }
next-commerce:dev: apiFetch called. query =  url =  __UNUSED__ queryData =  {
next-commerce:dev:   variables: { methodPath: 'products.list', arguments: [ {}, [Object] ] }
next-commerce:dev: } fetchOptions =  {}
next-commerce:dev: Looking for products.list in Spree Sdk.
next-commerce:dev: Checking part products.
next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/products?include=primary_variant%2Cvariants%2Cimages%2Coption_types%2Cvariants.option_values&per_page=6&image_transformation%5Bquality%5D=100&image_transformation%5Bsize%5D=1000x1000
next-commerce:dev: getAllPages called. Configuration:  query:  undefined userConfig:  { locale: 'en-US', locales: [ 'en-US', 'es' ] } preview:  undefined url:  undefined
next-commerce:dev: apiFetch called. query =  url =  __UNUSED__ queryData =  { variables: { methodPath: 'pages.list', arguments: [ [Object] ] } } fetchOptions =  {}
next-commerce:dev: Looking for pages.list in Spree Sdk.
next-commerce:dev: Checking part pages.
next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/cms_pages?per_page=500&filter%5Blocale_eq%5D=en-US
next-commerce:dev: getSiteInfo called. Configuration:  query:  undefined getSiteInfoVariables  {} config:  { locale: 'en-US', locales: [ 'en-US', 'es' ] }
next-commerce:dev: apiFetch called. query =  url =  __UNUSED__ queryData =  { variables: { methodPath: 'taxons.list', arguments: [ [Object] ] } } fetchOptions =  {}
next-commerce:dev: Looking for taxons.list in Spree Sdk.
next-commerce:dev: Checking part taxons.
next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/taxons?filter%5Bparent_permalink%5D=categories
next-commerce:dev: apiFetch called. query =  url =  __UNUSED__ queryData =  { variables: { methodPath: 'taxons.list', arguments: [ [Object] ] } } fetchOptions =  {}
next-commerce:dev: Looking for taxons.list in Spree Sdk.
next-commerce:dev: Checking part taxons.
next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/taxons?filter%5Bparent_permalink%5D=brands

aubryll · 2022-05-16T12:40:52Z

What help me, I run the command yarn in a ./packages/"api_backend_provider" then run the command yarn dev in site directory

@ashishkpaul run yarn dev in the root directory.

sir i am using spree 4.4 , can you guide me on these errors by running the command yarn dev

next-commerce:dev: event - compiled client and server successfully in 5s (889 modules)
next-commerce:dev: getAllProducts called. Configuration:  getAllProductsVariables:  { first: 6 } config:  { locale: 'en-US', locales: [ 'en-US', 'es' ] }
next-commerce:dev: apiFetch called. query =  url =  __UNUSED__ queryData =  {
next-commerce:dev:   variables: { methodPath: 'products.list', arguments: [ {}, [Object] ] }
next-commerce:dev: } fetchOptions =  {}
next-commerce:dev: Looking for products.list in Spree Sdk.
next-commerce:dev: Checking part products.
next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/products?include=primary_variant%2Cvariants%2Cimages%2Coption_types%2Cvariants.option_values&per_page=6&image_transformation%5Bquality%5D=100&image_transformation%5Bsize%5D=1000x1000
next-commerce:dev: getAllPages called. Configuration:  query:  undefined userConfig:  { locale: 'en-US', locales: [ 'en-US', 'es' ] } preview:  undefined url:  undefined
next-commerce:dev: apiFetch called. query =  url =  __UNUSED__ queryData =  { variables: { methodPath: 'pages.list', arguments: [ [Object] ] } } fetchOptions =  {}
next-commerce:dev: Looking for pages.list in Spree Sdk.
next-commerce:dev: Checking part pages.
next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/cms_pages?per_page=500&filter%5Blocale_eq%5D=en-US
next-commerce:dev: getSiteInfo called. Configuration:  query:  undefined getSiteInfoVariables  {} config:  { locale: 'en-US', locales: [ 'en-US', 'es' ] }
next-commerce:dev: apiFetch called. query =  url =  __UNUSED__ queryData =  { variables: { methodPath: 'taxons.list', arguments: [ [Object] ] } } fetchOptions =  {}
next-commerce:dev: Looking for taxons.list in Spree Sdk.
next-commerce:dev: Checking part taxons.
next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/taxons?filter%5Bparent_permalink%5D=categories
next-commerce:dev: apiFetch called. query =  url =  __UNUSED__ queryData =  { variables: { methodPath: 'taxons.list', arguments: [ [Object] ] } } fetchOptions =  {}
next-commerce:dev: Looking for taxons.list in Spree Sdk.
next-commerce:dev: Checking part taxons.
next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/taxons?filter%5Bparent_permalink%5D=brands

@ashishkpaul Where is the error? this is the same output I get on my installation, I am also using Spree 4.4. I would say ignore whatever you see there unless something is not working.

ashishkpaul · 2022-05-16T12:48:57Z

Thanks sir for your time and efforts, it would be very nice if u may write a production ready guide on it. Thanks again

…

On Mon, 16 May 2022, 18:11 Aubry Lungu, ***@***.***> wrote: What help me, I run the command yarn in a ./packages/"api_backend_provider" then run the command yarn dev in site directory @ashishkpaul <https://github.com/ashishkpaul> run yarn dev in the root directory. sir i am using spree 4.4 , can you guide me on these errors by running the command yarn dev next-commerce:dev: event - compiled client and server successfully in 5s (889 modules) next-commerce:dev: getAllProducts called. Configuration: getAllProductsVariables: { first: 6 } config: { locale: 'en-US', locales: [ 'en-US', 'es' ] } next-commerce:dev: apiFetch called. query = url = __UNUSED__ queryData = { next-commerce:dev: variables: { methodPath: 'products.list', arguments: [ {}, [Object] ] } next-commerce:dev: } fetchOptions = {} next-commerce:dev: Looking for products.list in Spree Sdk. next-commerce:dev: Checking part products. next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/products?include=primary_variant%2Cvariants%2Cimages%2Coption_types%2Cvariants.option_values&per_page=6&image_transformation%5Bquality%5D=100&image_transformation%5Bsize%5D=1000x1000 next-commerce:dev <https://stag.dingpack.com/api/v2/storefront/products?include=primary_variant%2Cvariants%2Cimages%2Coption_types%2Cvariants.option_values&per_page=6&image_transformation%5Bquality%5D=100&image_transformation%5Bsize%5D=1000x1000next-commerce:dev>: getAllPages called. Configuration: query: undefined userConfig: { locale: 'en-US', locales: [ 'en-US', 'es' ] } preview: undefined url: undefined next-commerce:dev: apiFetch called. query = url = __UNUSED__ queryData = { variables: { methodPath: 'pages.list', arguments: [ [Object] ] } } fetchOptions = {} next-commerce:dev: Looking for pages.list in Spree Sdk. next-commerce:dev: Checking part pages. next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/cms_pages?per_page=500&filter%5Blocale_eq%5D=en-US next-commerce:dev <https://stag.dingpack.com/api/v2/storefront/cms_pages?per_page=500&filter%5Blocale_eq%5D=en-USnext-commerce:dev>: getSiteInfo called. Configuration: query: undefined getSiteInfoVariables {} config: { locale: 'en-US', locales: [ 'en-US', 'es' ] } next-commerce:dev: apiFetch called. query = url = __UNUSED__ queryData = { variables: { methodPath: 'taxons.list', arguments: [ [Object] ] } } fetchOptions = {} next-commerce:dev: Looking for taxons.list in Spree Sdk. next-commerce:dev: Checking part taxons. next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/taxons?filter%5Bparent_permalink%5D=categories next-commerce:dev <https://stag.dingpack.com/api/v2/storefront/taxons?filter%5Bparent_permalink%5D=categoriesnext-commerce:dev>: apiFetch called. query = url = __UNUSED__ queryData = { variables: { methodPath: 'taxons.list', arguments: [ [Object] ] } } fetchOptions = {} next-commerce:dev: Looking for taxons.list in Spree Sdk. next-commerce:dev: Checking part taxons. next-commerce:dev: Calling the Spree API: GET https://stag.dingpack.com/api/v2/storefront/taxons?filter%5Bparent_permalink%5D=brands @ashishkpaul <https://github.com/ashishkpaul> Where is the error? this is the same output I get on my installation, I am also using Spree 4.4. I would say ignore whatever you see there unless something is not working. — Reply to this email directly, view it on GitHub <#681 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD4NU7ZVLYC3HYSTLHY6HXDVKI66HANCNFSM5OHNQWDA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

ashishkpaul · 2022-05-17T06:29:27Z

@aubryll hello sir, Front page loading successfully, but its not fetching the products from menu links

ashishkpaul · 2022-05-19T05:54:25Z

resolved by adding cors nginx policies on the side of spree hosted server
https://enable-cors.org/server_nginx.html
https://docs.viblast.com/player/cors/cors-on-nginx

This was referenced Feb 16, 2022

How to running in localhost? #684

Closed

Failed to load next.config.js #674

Closed

markuslewin mentioned this issue Apr 6, 2022

Import config with POSIX path #728

Merged

dominiksipowicz self-assigned this Apr 13, 2022

dominiksipowicz added the checking label Apr 13, 2022

dominiksipowicz closed this as completed Apr 13, 2022

dominiksipowicz removed the checking label Apr 13, 2022

dominiksipowicz removed their assignment Apr 13, 2022

michaelbromley mentioned this issue May 26, 2022

vendure custom checkout support #619 #714

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: Cannot find module '@vercel\commerce-local\next.config' #681

Error: Cannot find module '@vercel\commerce-local\next.config' #681

radgezito commented Feb 12, 2022

amir-zahedi commented Feb 13, 2022

Qwertin commented Feb 13, 2022

Dev05-Telnet commented Feb 15, 2022

MiguelMinoldo commented Feb 15, 2022

aubryll commented Feb 16, 2022

HeavenlyEntity commented Feb 19, 2022 •

edited

Loading

gregonarash commented Feb 20, 2022

sarathjasrin commented Feb 21, 2022

Varagos commented Feb 21, 2022

sarathjasrin commented Feb 22, 2022

timothyk0908 commented Mar 1, 2022

lukasmiller commented Mar 1, 2022 •

edited

Loading

CristianCucunuba commented Mar 3, 2022

OnlyC commented Mar 16, 2022

CrisleyAlves commented Mar 25, 2022 •

edited

Loading

GarlandM commented Mar 29, 2022

Shaffan commented Mar 29, 2022 •

edited

Loading

dominiksipowicz commented Apr 13, 2022

ashishkpaul commented May 16, 2022

aubryll commented May 16, 2022

ashishkpaul commented May 16, 2022

ashishkpaul commented May 16, 2022

aubryll commented May 16, 2022

ashishkpaul commented May 16, 2022 via email

ashishkpaul commented May 17, 2022

ashishkpaul commented May 19, 2022

Error: Cannot find module '@vercel\commerce-local\next.config' #681

Error: Cannot find module '@vercel\commerce-local\next.config' #681

Comments

radgezito commented Feb 12, 2022

amir-zahedi commented Feb 13, 2022

Qwertin commented Feb 13, 2022

Dev05-Telnet commented Feb 15, 2022

MiguelMinoldo commented Feb 15, 2022

aubryll commented Feb 16, 2022

HeavenlyEntity commented Feb 19, 2022 • edited Loading

gregonarash commented Feb 20, 2022

sarathjasrin commented Feb 21, 2022

Varagos commented Feb 21, 2022

sarathjasrin commented Feb 22, 2022

timothyk0908 commented Mar 1, 2022

lukasmiller commented Mar 1, 2022 • edited Loading

CristianCucunuba commented Mar 3, 2022

OnlyC commented Mar 16, 2022

CrisleyAlves commented Mar 25, 2022 • edited Loading

GarlandM commented Mar 29, 2022

Shaffan commented Mar 29, 2022 • edited Loading

dominiksipowicz commented Apr 13, 2022

ashishkpaul commented May 16, 2022

aubryll commented May 16, 2022

ashishkpaul commented May 16, 2022

ashishkpaul commented May 16, 2022

aubryll commented May 16, 2022

ashishkpaul commented May 16, 2022 via email

ashishkpaul commented May 17, 2022

ashishkpaul commented May 19, 2022

HeavenlyEntity commented Feb 19, 2022 •

edited

Loading

lukasmiller commented Mar 1, 2022 •

edited

Loading

CrisleyAlves commented Mar 25, 2022 •

edited

Loading

Shaffan commented Mar 29, 2022 •

edited

Loading