-
Notifications
You must be signed in to change notification settings - Fork 20
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
Unable to run a nodejs project as yarn is not present in path #456
Comments
Hi @anoop2811, thanks for the report. I have a couple of questions for you. (1) Do you have a (2) Are you expecting to use yarn2? If yes, paketo does not have yarn2 support yet. Please see the discussion here (paketo-buildpacks/yarn#19) |
Hi @arjun024 , yes, I do have a yarn.lock file at the root of the application and I am not using yarn2. |
Could you provide the build logs and a sample app if possible? |
Hi @arjun024,
|
Thanks for the sample and logs. As of now, the yarn-start buildpack only makes In the meantime, you can make use of the |
This change adds supports to cases where yarn is used in start commands. A common example is the use of yarn workspaces or frameworks (like lerna) built on top of yarn workspaces. A chose yarn command is run in a particular workspace using the following syntax: `yarn workspace <workspace_name> <command>` See https://classic.yarnpkg.com/en/docs/cli/workspace/ This requires the yarn tool to be available at launch time. See added integration test for an example. Also, see issue paketo-buildpacks/nodejs#456
This change is mostly cosmetic as node-engine buildpack provides both node and npm when node is requested. paketo-buildpacks/nodejs#456 This also makes the API consistent with the changes introduced in paketo-buildpacks/yarn-start#143 to yarn-install.
Thanks @arjun024 . but I still get the same error |
This change adds supports to cases where yarn is used in start commands. A common example is the use of yarn workspaces or frameworks (like lerna) built on top of yarn workspaces. A chose yarn command is run in a particular workspace using the following syntax: `yarn workspace <workspace_name> <command>` See https://classic.yarnpkg.com/en/docs/cli/workspace/ This requires the yarn tool to be available at launch time. See added integration test for an example. Also, see issue paketo-buildpacks/nodejs#456 Co-authored-by: Tim Hitchener <[email protected]>
@anoop2811 With v0.9.0 of the nodejs buildpack, you should be able to have |
What happened?
I have an application which requires yarn to start at run time but yarn is not present in the path in the run image.
What were you attempting to do?
Run application called backstage (backstage.io)
What did you expect to happen?
Expected it to run using the yarn start
What was the actual behavior? Please provide log output, if possible.
bash: yarn: command not found
Build Configuration
What platform (
pack
,kpack
,tekton
buildpacks plugin, etc.) are youusing? Please include a version.
pack build backstage-buildpack --path . --builder paketobuildpacks/builder:full
What buildpacks are you using? Please include versions.
Was using the packeto nodejs buildpack
What builder are you using? If custom, can you provide the output from
pack inspect-builder <builder>
?paketobuildpacks/builder:full
Can you provide a sample app or relevant configuration (
buildpack.yml
,nginx.conf
, etc.)?package copy.json.txt
Checklist
The text was updated successfully, but these errors were encountered: