-
## š Bug report
When adding bundle property to the meta.json file, that property doesn't go to the .qext file when making the build.
### Steps to Reproduce
1. Add the following to the meta.jsā¦
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
`run-script` with the `--workspaces` flag will run all workspace scripts, regardless if one sā¦
-
### Description :
I tried following the initial steps from README `npm run start:anvil`, `npm run deploy:core` this scripts ran nicely but when I run `npm run deploy:hello-world` I get this :
ā¦
-
When attempting to run docker-compose up, I encounter the following error during the build process:
```shell
=> [backend 9/11] RUN npm install ā¦
-
I tried run the example command, but I had the next error:
`> flashscore-scraping@1.1.1 start /content/FlashscoreScraping
> node src/index.js "country=brazil" "league=serie-a-2023" "headless"
ā¦
-
### Before opening, please confirm:
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-js/issues?q=is%3Aissue+) and [discussions](https://github.com/aws-amā¦
-
starting today, all deployments to google cloud run using the following command fail:
`gcloud run deploy --project --region --source . [... additonal service params]`
Root cause is that gcloā¦
-
```js
semver.satisfies(process.versions.node, '>=22.3.0')
```
There could even be a separate `node-s` for the https://nodejs.org/api/cli.html#--run command. It [does have limitations](https://nodejā¦
-
Allow to run OpenNext (**not Next**) locally for testing/debugging purposes with a simple command like `@opennextjs/aws local` or `@opennextjs/aws dev`
It should be relatively easy, as everything iā¦
-
### Issue description
This error below started happening recently-ish. A restart of the container fixes it.
```
npm notice
npm notice New major version of npm available! 8.19.4 -> 10.8.3
npmā¦