https://linen.dev logo
Join Slack
Powered by
How do I only run the Airybyte-webapp front end in...
# ask-community-for-troubleshooting
s
How do I only run the Airybyte-webapp front end in my local, since all other services are hosted in another machine?
k
Based on the knowledge sources provided, here's how you can run only the Airbyte webapp frontend locally: ## Running the Airbyte Webapp Frontend To develop features in the Airbyte Webapp locally, you need to: ### 1. Install Dependencies First, install the required tools: - Install [
nvm
](https://github.com/nvm-sh/nvm) (Node Version Manager) if not installed - Navigate to the webapp directory and install the required node version:
Copy code
cd airbyte-webapp nvm install
- Install the 
pnpm
package manager using Node's corepack:
Copy code
corepack enable && corepack install
### 2. Run the Webapp Start up the React app:
Copy code
pnpm install pnpm start
[Source: Webapp Contributions](https://docs.airbyte.com/platform/contributing-to-airbyte/developing-locally#webapp-contributions) Important Note: The documentation indicates that you need to "bring up an instance of Airbyte on TCP port 8001" before running the webapp. However, the knowledge sources don't explicitly explain how to configure the webapp to connect to a remote Airbyte instance hosted on another machine instead of localhost. The knowledge sources show how to run Airbyte locally on port 8001 using 
abctl local install --port 8001
, but they don't provide specific instructions for configuring the webapp to point to a remote backend server. You may need to configure environment variables or connection settings to point to your remote Airbyte instance, but this information is not available in the provided documentation.
s
@kapa.ai I did what you've said but not able to run got error
k
A message from kapa.ai
I'd be happy to help you troubleshoot the error you're encountering. However, I need more information to assist you effectively: 1. What specific error message are you seeing? Please share the complete error output. 2. Which step did the error occur at? Was it during: - Node/nvm installation? - 
pnpm install
? - 
pnpm start
? 3. What is your environment? (Operating system, Node version, etc.) Once you provide the error details, I can help you identify the issue and find a solution based on the available documentation. In the meantime, here are some common issues from the knowledge sources that might be relevant: - Build errors: Some users have encountered npm/build errors related to dependencies or node versions. The documentation mentions using specific node versions installed via 
nvm install
in the airbyte-webapp directory [Webapp Contributions](https://docs.airbyte.com/platform/contributing-to-airbyte/developing-locally#webapp-contributions). - Connection issues: If the webapp starts but can't connect to the backend, this could be because the webapp is trying to connect to localhost instead of your remote Airbyte instance. Unfortunately, the knowledge sources don't provide specific configuration details for this scenario. Please share the error message you're seeing so I can provide more targeted assistance.
s
@kapa.ai I got error when I try to start the service 
pnpm start
, I am using Node version of 20.19.0. The error I got is, > airbyte-webapp@ start /home/user/Documents/airbyte/airbyte-platform/airbyte-webapp > node ./scripts/start-dev.js ? Select your backend environment to develop against: Local (https://local.airbyte.dev) Selected environment: local 💡 Run pnpm start local to run against this environment without a select prompt. Cleaning gitignored files from generated directories... Generated directories cleanup complete. > airbyte-webapp@ generate-client /home/user/Documents/airbyte/airbyte-platform/airbyte-webapp > ./scripts/load-declarative-schema.sh && orval cat: ../airbyte-connector-builder-resources/CDK_VERSION: No such file or directory  ELIFECYCLE  Command failed with exit code 1. https://local.airbyte.dev > pnpm vite ✔️ Console Ninja extension is connected to Vite, see https://tinyurl.com/2vt8jxzw 🔨 Use build hash -dev- 📃 Connector docs are served remotely from GitHub. 📃 To work with local docs checkout https://github.com/airbytehq/airbyte next to your airbyte-platform or airbyte-platform-internal folder. 🤖 Generate generated-intents.ts file... error when starting dev server: Error: ENOENT: no such file or directory, open '/home/user/Documents/airbyte/airbyte-platform/airbyte-commons-auth/src/main/resources/intents.yaml' at Object.readFileUtf8 (/home/user/.vscode/extensions/wallabyjs.console-ninja-1.0.490/out/buildHook/index.js13592272) at Object.readFileSync (nodefs449:20) at PluginContext.buildStart (file///home/user/Documents/airbyte/airbyte platform/airbyte webapp/vite.config.mts.timestamp 1762230177493 71ae930493fae.mjs340:13) at PluginContainer.hookParallel (file:///home/user/Documents/airbyte/airbyte-platform/airbyte-webapp/node_modules/.pnpm/vite@5.4.18_@types+node@18.16.3_sass@1.70.0/node_modules/vite/dist/node/chunks/dep-DbT5NFX0.js4898839) at PluginContainer.buildStart (file:///home/user/Documents/airbyte/airbyte-platform/airbyte-webapp/node_modules/.pnpm/vite@5.4.18_@types+node@18.16.3_sass@1.70.0/node_modules/vite/dist/node/chunks/dep-DbT5NFX0.js4899512) at file:///home/user/Documents/airbyte/airbyte-platform/airbyte-webapp/node_modules/.pnpm/vite@5.4.18_@types+node@18.16.3_sass@1.70.0/node_modules/vite/dist/node/chunks/dep-DbT5NFX0.js6333323 at initServer (file:///home/user/Documents/airbyte/airbyte-platform/airbyte-webapp/node_modules/.pnpm/vite@5.4.18_@types+node@18.16.3_sass@1.70.0/node_modules/vite/dist/node/chunks/dep-DbT5NFX0.js633406) at httpServer.listen (file:///home/user/Documents/airbyte/airbyte-platform/airbyte-webapp/node_modules/.pnpm/vite@5.4.18_@types+node@18.16.3_sass@1.70.0/node_modules/vite/dist/node/chunks/dep-DbT5NFX0.js6334815) at file:///home/user/Documents/airbyte/airbyte-platform/airbyte-webapp/node_modules/.pnpm/vite@5.4.18_@types+node@18.16.3_sass@1.70.0/node_modules/vite/dist/node/chunks/dep-DbT5NFX0.js4560716
k
A message from kapa.ai
Based on the error messages you're seeing, there are two main issues preventing the webapp from starting: ## 1. Missing CDK_VERSION file The first error indicates:
Copy code
cat: ../airbyte-connector-builder-resources/CDK_VERSION: No such file or directory
This suggests that the 
airbyte-connector-builder-resources
directory or the 
CDK_VERSION
file within it is missing from your local setup. ## 2. Missing intents.yaml file The second error shows:
Copy code
Error: ENOENT: no such file or directory, open '/home/user/Documents/airbyte/airbyte-platform/airbyte-commons-auth/src/main/resources/intents.yaml'
This indicates that the 
intents.yaml
file in the 
airbyte-commons-auth
module is missing. ## Solution: Build the Complete Project First Based on the knowledge sources, it appears you need to build the entire Airbyte platform project before running just the webapp. The documentation mentions that for local development, you should: 1. Build the project first:
Copy code
./gradlew clean build
This will generate all the necessary files and dependencies that the webapp requires, including the missing 
CDK_VERSION
and 
intents.yaml
files. [Source: Resetting the Airbyte developer environment](https://docs.airbyte.com/platform/contributing-to-airbyte/developing-locally#resetting-the-airbyte-developer-environment) 2. Then run the webapp: After the build completes successfully, navigate to the webapp directory and run:
Copy code
cd airbyte-webapp pnpm install pnpm start
The issue you're encountering suggests that the webapp has dependencies on other parts of the Airbyte platform that need to be built first. Simply cloning the repository and trying to run the webapp alone won't work without these generated files.
j
Just forward the port—there isn't a stand -alone web app deployment anymore, it's served from 
airbyte-server
(and the builder from its component). You don't want to split these up or the kunernetes networking side will be a pain
Open in Slack
PreviousNext
Powered by