bun default build output directory (defined as CERC_BUILD_OUTPUT_DIR) is dist which should already be handled with pnpm support in the previously mentioned pull request
Installing bun using npm following our previous pnpm installation
npm install -g bun
We'll be using bun as a package manager that works with Node.js projects as defined in bun's docs
The bun CLI contains a Node.js-compatible package manager designed to be a dramatically faster replacement for npm, yarn, and pnpm. It's a standalone tool that will work in pre-existing Node.js projects; if your project has a package.json, bun install can help you speed up your workflow.
To test next.js apps using node.js and compatibility with all four packager managers -- npm, yarn, pnpm, and bun -- use the branches of snowball's nextjs-package-manager-example-app repo: nextjs-package-manager/npm, nextjs-package-manager/yarn, nextjs-package-manager/pnpm, nextjs-package-manager/bun.
This is working off pull request "[Add support for pnpm as a webapp build tool. #767](https://git.vdb.to/cerc-io/stack-orchestrator/pulls/767/files)" that adds `pnpm` package manager support for `nextjs` & `webapps`.
`bun` default build output directory (defined as `CERC_BUILD_OUTPUT_DIR`) is `dist` which should already be handled with `pnpm` support in the previously mentioned [pull request](https://git.vdb.to/cerc-io/stack-orchestrator/pulls/767/files)
Installing `bun` using `npm` following our previous `pnpm` installation
```zsh
npm install -g bun
```
We'll be using `bun` as a package manager that works with `Node.js` projects as defined in bun's [docs](https://bun.sh/docs/cli/install)
> The bun CLI contains a Node.js-compatible package manager designed to be a dramatically faster replacement for npm, yarn, and pnpm. It's a standalone tool that will work in pre-existing Node.js projects; if your project has a package.json, bun install can help you speed up your workflow.
To test `next.js` apps using `node.js` and compatibility with all four packager managers -- `npm`, `yarn`, `pnpm`, and `bun` -- use the branches of snowball's [nextjs-package-manager-example-app](https://git.vdb.to/snowball/nextjs-package-manager-example-app) repo: `nextjs-package-manager/npm`, `nextjs-package-manager/yarn`, `nextjs-package-manager/pnpm`, `nextjs-package-manager/bun`.
I don't actually know if it would work, just an idea
couldn't all these npm installs be combined?
`su ${USERNAME} -c "umask 0002 && npm install -g bun@1.1.x semver pnpm"`
I don't actually know if it would work, just an idea
As a guest contributor (plus as my first pull request and docker noob), I followed @telackey (approved by @dboreham) code style from the pnpm pull request & current code.
As a guest contributor (plus as my first pull request and docker noob), I followed @telackey (approved by @dboreham) code style from the [pnpm pull request](https://git.vdb.to/cerc-io/stack-orchestrator/pulls/767/files) & current code.
@telackey @dboreham your call.
Running npm several times is probably not much slower than running it once to install several packages.
The more important issue is to run all the commands in the same docker layer, which is being done.
Running npm several times is probably not much slower than running it once to install several packages.
The more important issue is to run all the commands in the same docker layer, which _is_ being done.
dboreham marked this conversation as resolved
VPhung24
requested review from telackey 2024-04-12 05:29:23 +00:00
VPhung24
self-assigned this 2024-04-12 05:29:34 +00:00
VPhung24
changed title from bun package management support for nextjs & webapps to Add support for bun as a webapp package manager2024-04-12 05:38:28 +00:00
dboreham
marked the pull request as work in progress 2024-04-12 13:51:07 +00:00
Currently the CI test uses this repo for its target app : https://git.vdb.to/cerc-io/test-progressive-web-app but perhaps we should switch to the multi-branch test app cited above now that we have three package managers to test?
Hi, this should be tested using a test like this one: https://git.vdb.to/cerc-io/stack-orchestrator/src/branch/main/tests/webapp-test/run-webapp-test.sh (can be run manually first, then we can talk about making a CI version).
Currently the CI test uses this repo for its target app : https://git.vdb.to/cerc-io/test-progressive-web-app but perhaps we should switch to the multi-branch test app cited above now that we have three package managers to test?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
jonathanface
telackey
dboreham
VPhung24
This is working off pull request "Add support for pnpm as a webapp build tool. #767" that adds
pnpmpackage manager support fornextjs&webapps.bundefault build output directory (defined asCERC_BUILD_OUTPUT_DIR) isdistwhich should already be handled withpnpmsupport in the previously mentioned pull requestInstalling
bunusingnpmfollowing our previouspnpminstallationWe'll be using
bunas a package manager that works withNode.jsprojects as defined in bun's docsTo test
next.jsapps usingnode.jsand compatibility with all four packager managers --npm,yarn,pnpm, andbun-- use the branches of snowball's nextjs-package-manager-example-app repo:nextjs-package-manager/npm,nextjs-package-manager/yarn,nextjs-package-manager/pnpm,nextjs-package-manager/bun.@@ -29,2 +29,4 @@# Install pnpm&& su ${USERNAME} -c "umask 0002 && npm install -g pnpm" \# Install bun&& su ${USERNAME} -c "umask 0002 && npm install -g bun@1.1.x" \couldn't all these npm installs be combined?
su ${USERNAME} -c "umask 0002 && npm install -g bun@1.1.x semver pnpm"I don't actually know if it would work, just an idea
As a guest contributor (plus as my first pull request and docker noob), I followed @telackey (approved by @dboreham) code style from the pnpm pull request & current code.
@telackey @dboreham your call.
Running npm several times is probably not much slower than running it once to install several packages.
The more important issue is to run all the commands in the same docker layer, which is being done.
bun package management support for nextjs & webappsto Add support for bun as a webapp package managerHi, this should be tested using a test like this one: https://git.vdb.to/cerc-io/stack-orchestrator/src/branch/main/tests/webapp-test/run-webapp-test.sh (can be run manually first, then we can talk about making a CI version).
Currently the CI test uses this repo for its target app : https://git.vdb.to/cerc-io/test-progressive-web-app but perhaps we should switch to the multi-branch test app cited above now that we have three package managers to test?