Building / installing from source not working

[Scorpoon]

Description

I don't know if it belongs here or to tteck's helper script but if i try to update from source i get an error that the constants.js module could not be found.
I guess the module should get installed automatically because of the package-lock.json?

Is it a bug or is it my fault? :D

homepage version

v0.8.12 (12ec1cf)

Installation method

Other (please describe above)

Configuration

No response

Container Logs

    __  __                                          
   / / / /___  ____ ___  ___  ____  ____ _____ ____ 
  / /_/ / __ \/ __ `__ \/ _ \/ __ \/ __ `/ __ `/ _ \
 / __  / /_/ / / / / / /  __/ /_/ / /_/ / /_/ /  __/
/_/ /_/\____/_/ /_/ /_/\___/ .___/\__,_/\__, /\___/ 
                          /_/          /____/       
Need to install the following packages:
update-browserslist-db@1.0.13
Ok to proceed? (y)-\-\
|Latest version:     1.0.30001611
Updating caniuse-lite version
$ pnpm up caniuse-lite
-caniuse-lite has been successfully updated

No target browser changes
/Lockfile is up to date, resolution step is skipped
\Already up to date
|Done in 1.3s
-
> startpage@0.1.0 build /opt/homepage
> next build

info  - Linting and checking validity of types  
info  - Creating an optimized production build  
info  - Compiled successfully
info  - Collecting page data ..\Error: Cannot find module '../../next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/shared/lib/constants.js'
Require stack:
- /opt/homepage/.next/server/pages/_document.js
- /opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/server/require.js
- /opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/server/load-components.js
- /opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/export/worker.js
- /opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/build/worker.js
- /opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/jest-worker/processChild.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1143:15)
    at mod._resolveFilename (/opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/build/webpack/require-hook.js:27:32)
    at mod._resolveFilename (/opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/build/webpack/require-hook.js:27:32)
    at Module._load (node:internal/modules/cjs/loader:984:27)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at require (node:internal/modules/helpers:179:18)
    at 1880 (/opt/homepage/.next/server/pages/_document.js:77:18)
    at __webpack_require__ (/opt/homepage/.next/server/webpack-runtime.js:25:42)
    at 7505 (/opt/homepage/.next/server/chunks/9589.js:18:18)
    at __webpack_require__ (/opt/homepage/.next/server/webpack-runtime.js:25:42) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/opt/homepage/.next/server/pages/_document.js',
    '/opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/server/require.js',
    '/opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/server/load-components.js',
    '/opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/export/worker.js',
    '/opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/build/worker.js',
    '/opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/compiled/jest-worker/processChild.js'
  ]
}

> Build error occurred
Error: Failed to collect page data for /browserconfig.xml
    at /opt/homepage/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0__react@18.2.0/node_modules/next/dist/build/utils.js:916:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  type: 'Error'
}
info  - Collecting page data | ELIFECYCLE  Command failed with exit code 1.

[ERROR] in line 75: exit code 0: while executing command pnpm build

Browser Logs

No response

Troubleshooting

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the error message you've provided, it seems like there is an issue with the constants.js module not being found during the build process. This could be due to a variety of reasons, such as a corrupted node_modules directory, an issue with the package-lock.json, or a problem with the Next.js build process itself.

Here are a few steps you can take to troubleshoot this issue:

1. Clear node_modules and reinstall: Sometimes, the node_modules directory can become corrupted. You can try deleting the node_modules directory and the pnpm-lock.yaml file, then reinstalling the dependencies:

   rm -rf node_modules
   rm pnpm-lock.yaml
   pnpm install

2. Check for updates: Ensure that you are using the latest version of Homepage and all dependencies are up to date. You can check for updates in the repository and pull the latest changes if necessary.

3. Check package-lock.json: If you suspect an issue with package-lock.json, you can try regenerating it by deleting it and running pnpm install again to create a fresh one.

4. Review the build script: If you are using a custom script to build Homepage, make sure that it is up to date with the latest instructions from the Homepage documentation.

5. Consult the documentation: Review the Homepage documentation and the GitHub repository for any specific build instructions or known issues that might be related to your problem.

6. Seek support: If the issue persists, you can seek support by starting a discussion on the Homepage Discussions page or checking if others have encountered similar issues.

Remember to replace any sensitive information in your logs or configuration files before sharing them publicly for troubleshooting.

If you've already tried these steps or if there's more specific information about the error, please provide additional details so that I can assist you further.

This comment was generated by Glime.

[Scorpoon]

Removing node_modules and package-lock.json and then reinstalling the dependencies worked.

Tried then to "update" again with the tteck helper script (which pulls always the latest release) and it works now.
Nice bot btw ;)

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.