Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm run build error - core 0.1.5 #138

Closed
1 task done
thim81 opened this issue Jan 28, 2022 · 1 comment
Closed
1 task done

npm run build error - core 0.1.5 #138

thim81 opened this issue Jan 28, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@thim81
Copy link
Contributor

thim81 commented Jan 28, 2022

Have you read the Contributing Guidelines on issues?

Description

@eventcatalog/core@0.1.5 build
next build && next export

warn - No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

info - Checking validity of types...
It looks like you're trying to use TypeScript but do not have the required package(s) installed.

Please install @types/node by running:

npm install --save-dev @types/node

If you are not trying to use TypeScript, please remove the tsconfig.json file from your package root (and any TypeScript files in your pages directory).

Error: Command failed: cross-env PROJECT_DIR=/home/vsts/work/1/s/event-catalog npm run build
at checkExecSyncError (node:child_process:826:11)
at execSync (node:child_process:900:15)
at Command. (/home/vsts/work/1/s/event-catalog/node_modules/@eventcatalog/core/bin/eventcatalog.js:60:5)
at Command.listener [as _actionHandler] (/home/vsts/work/1/s/event-catalog/node_modules/commander/index.js:922:31)
at Command._parseCommand (/home/vsts/work/1/s/event-catalog/node_modules/commander/index.js:1503:14)
at Command._dispatchSubcommand (/home/vsts/work/1/s/event-catalog/node_modules/commander/index.js:1443:18)
at Command._parseCommand (/home/vsts/work/1/s/event-catalog/node_modules/commander/index.js:1460:12)
at Command.parse (/home/vsts/work/1/s/event-catalog/node_modules/commander/index.js:1292:10)
at run (/home/vsts/work/1/s/event-catalog/node_modules/@eventcatalog/core/bin/eventcatalog.js:115:7)
at Object. (/home/vsts/work/1/s/event-catalog/node_modules/@eventcatalog/core/bin/eventcatalog.js:122:1) {

Steps to reproduce

Do a clean install and try to run npm run build

Expected behavior

Succesfully build event catalog

Actual behavior

see the error in the description

Your environment

  • EventCatalog version used: 0.1.5
  • Environment name and version (e.g. Chrome 89, Node.js 16.4): NodeJS 16.0
  • Operating system and version (e.g. Ubuntu 20.04.2 LTS): Ubuntu 20.04.2 LTS
@thim81 thim81 added the bug Something isn't working label Jan 28, 2022
@thim81
Copy link
Contributor Author

thim81 commented Jan 28, 2022

Since I had a event catalog running, it was missing a dependency

Steps that fixed it:

  • removed the node_modules, .eventcatalog-core, .next folders
  • removed package-lock.json
  • added "@types/node" to by running: npm install --save-dev @types/node
  • ran npm install
  • ran successfully npm run build

@thim81 thim81 closed this as completed Jan 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant