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

[Bug report] pnpm build fails with error #1623

Closed
justinmclean opened this issue Jan 21, 2024 · 11 comments · Fixed by #1626
Closed

[Bug report] pnpm build fails with error #1623

justinmclean opened this issue Jan 21, 2024 · 11 comments · Fixed by #1626
Assignees

Comments

@justinmclean
Copy link
Member

Describe what's wrong

pnpm build fails with error on latest main.

Error message and/or stacktrace

.next/types/app/(home)/page.ts:2:24
Type error: Cannot find module '../../../../app/(home)/page.js' or its corresponding type declarations.

  1 | // File: /Users/justin/gravitino/web/app/(home)/page.js
> 2 | import * as entry from '../../../../app/(home)/page.js'
    |                        ^
  3 | import type { ResolvingMetadata, ResolvingViewport } from 'next/dist/lib/metadata/types/metadata-interface.js'
  4 |
  5 | type TEntry = typeof import('../../../../app/(home)/page.js')
 ELIFECYCLE  Command failed with exit code 1.
justin@Justins-MBP web % 

How to reproduce

Try to build Gravitino Web UI

Additional context

No response

@justinmclean
Copy link
Member Author

I did do this, so that's not the issue:

pnpm install
Lockfile is up to date, resolution step is skipped
Already up to date
Done in 508ms

@justinmclean
Copy link
Member Author

It seems that doing a top-level clean build fixes this issue.

@ch3yne
Copy link
Contributor

ch3yne commented Jan 22, 2024

using pnpm dist instead of pnpm build.
I will revise the document description.

@justinmclean
Copy link
Member Author

I'm not sure if pnpm dist is correct as I get 500:Internal Error in the Gravitino Web UI

@ch3yne
Copy link
Contributor

ch3yne commented Jan 22, 2024

I'm not sure if pnpm dist is correct as I get 500:Internal Error in the Gravitino Web UI

Can you paste some pictures or error outputs about this?

The latest submitted code no longer includes the (home) path.
Make sure you have pulled the latest code. If it still doesn't work, try deleting the .next folder and running it again.

@justinmclean
Copy link
Member Author

Sure:
image
image
image

@justinmclean
Copy link
Member Author

Looks like its using port 3000 rather than 8090 to connect to Gavitino?

@ch3yne
Copy link
Contributor

ch3yne commented Jan 22, 2024

Looks like its using port 3000 rather than 8090 to connect to Gavitino?

If you need to make changes to the web, you'll have to start the development environment with debugging enabled, and the port to use is 3000.
If you're just using it, you don't need to start the development server, you can just access it using port 8090.

@justinmclean
Copy link
Member Author

justinmclean commented Jan 22, 2024

I also tried with pnpm dev and the some error occurs and the Gravitino Web UI fails to start.

@ch3yne
Copy link
Contributor

ch3yne commented Jan 22, 2024

Can I ask what Ollama in the browser title is? Will it conflict with other services?

@justinmclean
Copy link
Member Author

It runs on port 3000, but it been turned off. If it is running the Webb UI starts on port 3001. I think the icon is just cached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants