firebase: Initialise firebase setup by juliaogris · Pull Request #2 · evylang/evy

juliaogris · 2022-08-16T02:10:11Z

Add required tooling for firebase - firebase CLI and jre - with hermit.

Follow firebase init prompt to create hosting setup, GitHub actions
and emulator setup.

Initial manual deployment: https://evy.dev

Hermit install firebase 11.6.0 with hermit install firebase

Run `firebase init` and follow prompts with best intentions to avoid chaos 🤷‍♀️.

github-actions · 2022-08-16T02:17:20Z

Visit the preview URL for this PR (updated for commit 03315e6):

https://evy-lang--pr2-firebase-init-f3we64qt.web.app

_{(expires Tue, 23 Aug 2022 02:20:43 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

Use firebase boilerplate .html pages, initially written to out/public and move them to source directory `frontend`. Later we will use `frontend` for frontend source code, probably written in SvelteJS. Add make targets for frontend builds and firebase tests and deployment. firebase puts various log files alongside the firebase.json which really bloats the root directory, so move everything firebase related to `firebase`. In order to start the emulator with `make firebase-test` java is required so install openjre with hermit: hermit install openjre Signed-off-by: Julia Ogris <julia.ogris@gmail.com>

camh-

🌲 LGTM

- Upgrade hermitised tools - Check go dependencies (nothing to be done) - Upgrade node dependencies - Upgrade playwright docker image HOORAY, all upgraded. This merges the following commits: * tools: Upgrade tools with hermit * tools: Upgrade npm tooling * tools: Manually update playwright docker image version .hermit/node/package-lock.json | 16 ++++++------ .hermit/node/package.json | 4 +-- Makefile | 2 +- ...rebase-13.0.2.pkg => .firebase-13.1.0.pkg} | 0 bin/{.gh-2.42.1.pkg => .gh-2.43.1.pkg} | 0 bin/{.go-1.21.5.pkg => .go-1.21.6.pkg} | 0 ...{.gofumpt-0.5.0.pkg => .gofumpt-0.6.0.pkg} | 0 bin/{.node-21.5.0.pkg => .node-21.6.1.pkg} | 0 ...1.0.16.1_1.pkg => .openjre-18.0.2.1_1.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/gofumpt | 2 +- bin/jaotc | 1 - bin/java | 2 +- bin/jfr | 2 +- bin/jjs | 1 - bin/jrunscript | 2 +- bin/jwebserver | 1 + bin/keytool | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- bin/pack200 | 1 - bin/rmid | 1 - bin/rmiregistry | 2 +- bin/unpack200 | 1 - e2e/package-lock.json | 26 +++++++++---------- e2e/package.json | 4 +-- 31 files changed, 41 insertions(+), 45 deletions(-) Pull-Request: #261

Update hermitised tools with tools hermit upgrade Ensure that node, openjre and firebase don't have new major versions. Upgrade npm packages with ncu. (cd .hermit/node/; ncu -u; npm install) ncu is a node upgrading tool, previously installed globally with `npm install --global npm-check-updates`. We are not upgrading playwright because screenshot tests fail with newer version in un-reproducible ways. Add manual fixes in follow up commit. This merges the following commits: * all: Upgrade tools (automated) * all: Upgrade tools .hermit/node/package-lock.json | 105 ++++++++++-------- .hermit/node/package.json | 2 +- Makefile | 2 +- ...rebase-13.1.0.pkg => .firebase-13.6.0.pkg} | 0 bin/{.gh-2.43.1.pkg => .gh-2.46.0.pkg} | 0 bin/{.go-1.21.6.pkg => .go-1.22.1.pkg} | 0 ...t-1.55.2.pkg => .golangci-lint-1.57.2.pkg} | 0 ...aser-1.23.0.pkg => .goreleaser-1.24.0.pkg} | 0 bin/{.node-21.6.1.pkg => .node-21.7.1.pkg} | 0 ...check-0.9.0.pkg => .shellcheck-0.10.0.pkg} | 0 bin/{.shfmt-3.7.0.pkg => .shfmt-3.8.0.pkg} | 0 ...{.tinygo-0.30.0.pkg => .tinygo-0.31.2.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- bin/shellcheck | 2 +- bin/shfmt | 2 +- bin/tinygo | 2 +- go.mod | 2 +- main.go | 2 +- pkg/evaluator/builtin.go | 4 +- pkg/evaluator/evaluator_test.go | 16 +-- pkg/lexer/lexer_test.go | 9 +- pkg/parser/format.go | 2 +- pkg/parser/format_test.go | 11 -- 32 files changed, 81 insertions(+), 100 deletions(-) Pull-request: #322

Upgrade tooling and dependencies with hermit upgrade go get -u go mod tidy We don't update node tools here because they need more care manual update to the e2e test. This merges the following commits: * hermit: Upgrade tools * go: Upgrade packages with .golangci.yaml | 2 ++ ...irebase-13.6.0.pkg => .firebase-13.9.0.pkg} | 0 bin/{.gh-2.46.0.pkg => .gh-2.49.2.pkg} | 0 bin/{.go-1.22.1.pkg => .go-1.22.3.pkg} | 0 ...nt-1.57.2.pkg => .golangci-lint-1.58.1.pkg} | 0 ...easer-1.24.0.pkg => .goreleaser-1.26.1.pkg} | 0 bin/{.node-21.7.1.pkg => .node-21.7.3.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- docs/usage.md | 18 +++++++++--------- frontend/docs/usage.html | 18 +++++++++--------- go.mod | 2 +- go.sum | 12 ++++++------ main.go | 10 +++++----- 22 files changed, 42 insertions(+), 40 deletions(-) Pull-request: #346

Do the monthly tool-upgrade dance: - hermit - go - node and fix manually issues that arose - this time quite few 🎉. This merges the following commits: * all: Fix URLs in Markdown files * bin: Upgrade hermitised tools * go: Upgrade go dependencies * node: Upgrade node tooling .golangci.yaml | 10 - .hermit/node/package-lock.json | 590 +++--------------- .hermit/node/package.json | 4 +- Makefile | 2 +- ...ebase-13.9.0.pkg => .firebase-13.10.2.pkg} | 0 bin/{.gh-2.49.2.pkg => .gh-2.50.0.pkg} | 0 ...t-1.58.1.pkg => .golangci-lint-1.59.0.pkg} | 0 ...aser-1.26.1.pkg => .goreleaser-1.26.2.pkg} | 0 bin/firebase | 2 +- bin/gh | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- e2e/package-lock.json | 26 +- e2e/package.json | 4 +- examples/README.md | 2 +- go.mod | 4 +- go.sum | 12 +- learn/README.md | 4 +- learn/go.mod | 6 +- learn/go.sum | 4 +- pkg/cli/runtime.go | 2 +- 21 files changed, 120 insertions(+), 558 deletions(-) Pull-request: #371

The usual, but this time documented: - upgrade hermitised tools - upgrade go deps (more effort this time) - upgrade npm deps - upgrade playwright (yay, easy this time) - add documentation on upgrading This merges the following commits: * all: Upgrade hermitised tools * all: Upgrade go dependencies * all: Upgrade npm packages of tools used * docs: Add upgrade guide to developer docs * docs: Add upgrade guide to developer docs (generated) .goreleaser.yaml | 1 + .hermit/node/package-lock.json | 145 ++++++----- .hermit/node/package.json | 6 +- Makefile | 2 +- ...base-13.10.2.pkg => .firebase-13.15.1.pkg} | 0 bin/{.gh-2.50.0.pkg => .gh-2.54.0.pkg} | 0 bin/{.go-1.22.3.pkg => .go-1.22.6.pkg} | 0 ...t-1.59.0.pkg => .golangci-lint-1.59.1.pkg} | 0 ...easer-1.26.2.pkg => .goreleaser-2.1.0.pkg} | 0 bin/{.node-21.7.3.pkg => .node-22.6.0.pkg} | 0 ...{.tinygo-0.31.2.pkg => .tinygo-0.32.0.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- bin/tinygo | 2 +- build-tools/md/main.go | 4 +- docs/development/upgrade.md | 132 ++++++++++ e2e/package-lock.json | 36 +-- e2e/package.json | 4 +- frontend/docs/development/upgrade.html | 232 ++++++++++++++++++ frontend/docs/development/upgrade.htmlf | 136 ++++++++++ go.mod | 10 +- go.sum | 12 +- learn/go.mod | 12 +- learn/go.sum | 12 +- learn/pkg/learn/course.go | 2 +- learn/pkg/learn/markdown.go | 10 +- learn/pkg/learn/question.go | 2 +- learn/pkg/learn/renderer.go | 15 +- learn/pkg/learn/unit.go | 2 +- pkg/md/md.go | 9 +- pkg/md/undecorate.go | 54 ++++ pkg/md/undecorate_test.go | 88 +++++++ 40 files changed, 812 insertions(+), 136 deletions(-) Pull-request: #410

Upgrade deps and tooling as described in docs/development/upgrade.md. Refine the documentation along the way and add a last manual step ensuring all external URLs still work. The recent upgrade wasn't long ago, but firebase had an upgrade which nagged on every local deploy and go had a new release as well, so I thought, let's just get it done. Most things went smooth this time, except for the golangci-lint upgrade. This merges the following commits: * tools: Upgrade hermitised tools * go: Upgrade go dependencies * tools: Upgrade frontend node tooling * tools: Upgrade Playwright * tools: Document external link check .golangci.yaml | 1 + .hermit/node/package-lock.json | 95 ++++++++++--------- .hermit/node/package.json | 2 +- Makefile | 2 +- ...base-13.15.1.pkg => .firebase-13.15.4.pkg} | 0 bin/{.gh-2.54.0.pkg => .gh-2.55.0.pkg} | 0 bin/{.go-1.22.6.pkg => .go-1.23.0.pkg} | 0 ...{.gofumpt-0.6.0.pkg => .gofumpt-0.7.0.pkg} | 0 ...t-1.59.1.pkg => .golangci-lint-1.60.3.pkg} | 0 ...leaser-2.1.0.pkg => .goreleaser-2.2.0.pkg} | 0 bin/{.node-22.6.0.pkg => .node-22.7.0.pkg} | 0 bin/{.shfmt-3.8.0.pkg => .shfmt-3.9.0.pkg} | 0 ...{.tinygo-0.32.0.pkg => .tinygo-0.33.0.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/gofumpt | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- bin/shfmt | 2 +- bin/tinygo | 2 +- docs/development/upgrade.md | 27 ++++-- e2e/package-lock.json | 26 ++--- e2e/package.json | 4 +- frontend/docs/development/upgrade.html | 28 ++++-- frontend/docs/development/upgrade.htmlf | 27 ++++-- frontend/learn/foundation/sequence/evy.html | 2 +- frontend/learn/foundation/sequence/evy.htmlf | 2 +- go.mod | 4 +- learn/content/foundation/sequence/evy.md | 2 +- learn/go.mod | 6 +- learn/pkg/learn/encrypt.go | 6 +- pkg/bytecode/code.go | 2 +- pkg/bytecode/instructions.go | 2 +- pkg/md/testdata/sample/README.md | 2 +- 40 files changed, 151 insertions(+), 115 deletions(-) Pull-request: #422

Add govulncheck to lint-go target, provided by the Go core team. I just did the Go developer survey and they asked about whether I know about it and use it. I did not really know about it, but it seems knowing about vulnerabilities early is what we want. The current result when running the check is: No vulnerabilities found. Your code is affected by 0 vulnerabilities. This scan also found 0 vulnerabilities in packages you import and 3 vulnerabilities in modules you require, but your code doesn't appear to call these vulnerabilities. Vulnerability #1: GO-2024-3107 Stack exhaustion in Parse in go/build/constraint More info: https://pkg.go.dev/vuln/GO-2024-3107 Standard library Found in: stdlib@go1.23 Fixed in: stdlib@go1.23.1 Vulnerability #2: GO-2024-3106 Stack exhaustion in Decoder.Decode in encoding/gob More info: https://pkg.go.dev/vuln/GO-2024-3106 Standard library Found in: stdlib@go1.23 Fixed in: stdlib@go1.23.1 Vulnerability #3: GO-2024-3105 Stack exhaustion in all Parse functions in go/parser More info: https://pkg.go.dev/vuln/GO-2024-3105 Standard library Found in: stdlib@go1.23 Fixed in: stdlib@go1.23.1

Add govulncheck to lint-go target, provided by the Go core team. I just did the Go developer survey and they asked about whether I know about it and use it. I did not really know about it, but it seems knowing about vulnerabilities early is what we want. The current result when running the check is: No vulnerabilities found. Your code is affected by 0 vulnerabilities. This scan also found 0 vulnerabilities in packages you import and 3 vulnerabilities in modules you require, but your code doesn't appear to call these vulnerabilities. Vulnerability #1: GO-2024-3107 Stack exhaustion in Parse in go/build/constraint More info: https://pkg.go.dev/vuln/GO-2024-3107 Standard library Found in: stdlib@go1.23 Fixed in: stdlib@go1.23.1 Vulnerability #2: GO-2024-3106 Stack exhaustion in Decoder.Decode in encoding/gob More info: https://pkg.go.dev/vuln/GO-2024-3106 Standard library Found in: stdlib@go1.23 Fixed in: stdlib@go1.23.1 Vulnerability #3: GO-2024-3105 Stack exhaustion in all Parse functions in go/parser More info: https://pkg.go.dev/vuln/GO-2024-3105 Standard library Found in: stdlib@go1.23 Fixed in: stdlib@go1.23.1 Pull-request: #437

Our regular housekeeping task: upgrade all the tools. Firebase and node are now more insistent with their nag-ware to upgrade, even using color. What can I say. It works. This time was relatively easy, no manual intervention require. I followed the docs at to a tea, and it all worked fine. This merges the following commits: * tools: Upgrade hermitised tools * go: Upgrade all go dependencies * npm: Upgrade node tools * playwright: Upgrade end-to-end testing tool .hermit/node/package-lock.json | 30 +++++++++++-------- .hermit/node/package.json | 2 +- Makefile | 2 +- bin/{.fd-10.1.0.pkg => .fd-10.2.0.pkg} | 0 ...base-13.15.4.pkg => .firebase-13.17.0.pkg} | 0 bin/{.gh-2.55.0.pkg => .gh-2.56.0.pkg} | 0 bin/{.go-1.23.0.pkg => .go-1.23.1.pkg} | 0 ...t-1.60.3.pkg => .golangci-lint-1.61.0.pkg} | 0 ...leaser-2.2.0.pkg => .goreleaser-2.3.1.pkg} | 0 bin/{.node-22.7.0.pkg => .node-22.8.0.pkg} | 0 bin/corepack | 2 +- bin/fd | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- e2e/package-lock.json | 26 ++++++++-------- e2e/package.json | 4 +-- go.mod | 6 ++-- go.sum | 16 +++++----- learn/go.mod | 8 ++--- learn/go.sum | 16 +++++----- 27 files changed, 69 insertions(+), 63 deletions(-) Link: https://docs.evy.dev/development/upgrade.html Pull-request: #443

Upgrade tools and dependencies according to docs. - Upgrade Hermitised Tools: automation only - Upgrade Go Dependencies: automation only - Upgrade Frontend Tools: nothing to be done - Test External URLs: make URL grep command more robust - Upgrade Playwright: this one was painful For the playwright upgrade we also upgraded Ubuntu version from jammy to noble. Many snapshot PNGs had to be updated as well with `make snaps USE_DOCKER=1`. Changes are barely visible, they seem to relate to pixel level changes. I tried really hard to get the local runs to work on my Ubuntu 24.04 (noble) system, but something with Webkit is not working as in Docker locally. I have abandoned trying to fix this for now. Docker and CI end-to-end tests seem to work reliably. This merges the following commits: * hermit: Upgrade tools * go: Update dependencies * make: Improve test-urls target * playwright: Upgrade Makefile | 4 +-- ...base-13.17.0.pkg => .firebase-13.22.0.pkg} | 0 bin/{.gh-2.56.0.pkg => .gh-2.58.0.pkg} | 0 bin/{.go-1.23.1.pkg => .go-1.23.2.pkg} | 0 ...leaser-2.3.1.pkg => .goreleaser-2.3.2.pkg} | 0 bin/{.node-22.8.0.pkg => .node-22.9.0.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- .../comment-hover-chromium-docker.png | Bin 93302 -> 93311 bytes .../comment-page-chromium-docker.png | Bin 72179 -> 72187 bytes .../dialog-chromium-docker.png | Bin 57631 -> 57654 bytes .../dialog-theme-chromium-docker.png | Bin 62197 -> 62238 bytes .../expand-0-chromium-docker.png | Bin 93735 -> 93739 bytes .../expand-1-chromium-docker.png | Bin 93303 -> 93320 bytes .../no-dialog-chromium-docker.png | Bin 74294 -> 74311 bytes .../printf-chromium-docker.png | Bin 90526 -> 90835 bytes .../printf-theme-chromium-docker.png | Bin 86661 -> 86813 bytes .../start-chromium-docker.png | Bin 74294 -> 74311 bytes .../start-theme-chromium-docker.png | Bin 71717 -> 71730 bytes e2e/package-lock.json | 26 +++++++++--------- e2e/package.json | 4 +-- .../modal-chromium-docker.png | Bin 64267 -> 64241 bytes .../landing-bottom-chromium-docker.png | Bin 22952 -> 22952 bytes .../landing-top-chromium-docker.png | Bin 27627 -> 24830 bytes go.mod | 4 +-- go.sum | 8 +++--- learn/go.mod | 6 ++-- learn/go.sum | 8 +++--- 35 files changed, 39 insertions(+), 39 deletions(-) Link: https://docs.evy.dev/development/upgrade.html Pull-request: #447

Upgrade tooling according to https://docs.evy.dev/development/upgrade.html Everything went fairly smoothly this time. There were only a few new golangci-lint warning, due to the new linter recvcheck. I had to manually fix those. Playwright update for Docker worked out of the box, the local playwright version is sadly still broken. This merges the following commits: * hermit: Upgrade tools * go: Update dependencies * node: Upgrade tools * playwright: Upgrade .golangci.yaml | 2 - .hermit/node/package-lock.json | 148 +++++++++--------- .hermit/node/package.json | 2 +- Makefile | 2 +- ...base-13.22.0.pkg => .firebase-13.25.0.pkg} | 0 bin/{.gh-2.58.0.pkg => .gh-2.61.0.pkg} | 0 bin/{.go-1.23.2.pkg => .go-1.23.3.pkg} | 0 ...t-1.61.0.pkg => .golangci-lint-1.62.0.pkg} | 0 ...leaser-2.3.2.pkg => .goreleaser-2.4.4.pkg} | 0 bin/{.node-22.9.0.pkg => .node-22.11.0.pkg} | 0 bin/{.shfmt-3.9.0.pkg => .shfmt-3.10.0.pkg} | 0 ...{.tinygo-0.33.0.pkg => .tinygo-0.34.0.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- bin/shfmt | 2 +- bin/tinygo | 2 +- e2e/package-lock.json | 26 +-- e2e/package.json | 4 +- go.mod | 6 +- go.sum | 16 +- learn/go.mod | 8 +- learn/go.sum | 16 +- learn/pkg/learn/frontmatter.go | 16 +- pkg/evaluator/evaluator.go | 2 +- 32 files changed, 132 insertions(+), 140 deletions(-) Pull-request: #454

Upgrade hermitised and node tools according to docs. It all went smoothly apart from Playwright which required a bunch of snapshot updates again and is still not working properly. This merges the following commits: * tools: Upgrade hermitised tools * node: Upgrade tooling * tools: Upgrade Playwright .hermit/node/package-lock.json | 195 ++++++++---------- .hermit/node/package.json | 4 +- Makefile | 2 +- ...base-13.25.0.pkg => .firebase-13.29.1.pkg} | 0 bin/{.gh-2.61.0.pkg => .gh-2.63.2.pkg} | 0 bin/{.go-1.23.3.pkg => .go-1.23.4.pkg} | 0 ...t-1.62.0.pkg => .golangci-lint-1.62.2.pkg} | 0 ...leaser-2.4.4.pkg => .goreleaser-2.5.0.pkg} | 0 bin/{.node-22.11.0.pkg => .node-22.12.0.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- .../comment-hover-ios-docker.png | Bin 32347 -> 52152 bytes .../comment-page-ios-docker.png | Bin 22732 -> 33290 bytes .../test.js-snapshots/expand-0-ios-docker.png | Bin 30321 -> 52209 bytes .../test.js-snapshots/expand-1-ios-docker.png | Bin 31574 -> 52173 bytes .../test.js-snapshots/printf-ios-docker.png | Bin 40450 -> 73996 bytes .../test.js-snapshots/sidebar-ios-docker.png | Bin 20539 -> 28964 bytes .../test.js-snapshots/start-ios-docker.png | Bin 49463 -> 78726 bytes e2e/package-lock.json | 26 +-- e2e/package.json | 4 +- .../about-dialog-ios-docker.png | Bin 33572 -> 49331 bytes .../console-output-ios-docker.png | Bin 14475 -> 15293 bytes .../test.js-snapshots/modal-ios-docker.png | Bin 43982 -> 52656 bytes .../no-dialog-chromium-docker.png | Bin 29491 -> 29669 bytes .../no-dialog-ios-docker.png | Bin 21357 -> 27926 bytes .../no-sidebar-ios-docker.png | Bin 21357 -> 27926 bytes .../read-input-chromium-docker.png | Bin 25043 -> 25003 bytes .../read-input-ios-docker.png | Bin 16756 -> 20988 bytes .../test.js-snapshots/sidebar-ios-docker.png | Bin 17099 -> 19429 bytes .../landing-top-ios-docker.png | Bin 14986 -> 15768 bytes .../playground-chromium-docker.png | Bin 29490 -> 29669 bytes .../playground-ios-docker.png | Bin 21357 -> 27926 bytes 40 files changed, 118 insertions(+), 133 deletions(-) docs: https://github.com/evylang/evy/blob/5b196cbe154c60d68b2c2deffa41e118985ffba9/docs/development/upgrade.md Pull-request: #459

Upgrade hermitised and node tools according to docs. It all went smoothly apart from Playwright which required a bunch of snapshot updates again and is still not working properly with local Node run on Linux :(. This merges the following commits: * tools: Upgrade hermitised tools * node: Upgrade tooling * go: Upgrade dependencies * tools: Upgrade Playwright .hermit/node/package-lock.json | 217 ++++++++++++------ .hermit/node/package.json | 4 +- Makefile | 2 +- ...base-13.29.1.pkg => .firebase-13.29.2.pkg} | 0 bin/{.gh-2.63.2.pkg => .gh-2.65.0.pkg} | 0 bin/{.go-1.23.4.pkg => .go-1.23.5.pkg} | 0 ...t-1.62.2.pkg => .golangci-lint-1.63.4.pkg} | 0 ...leaser-2.5.0.pkg => .goreleaser-2.6.1.pkg} | 0 bin/{.node-22.12.0.pkg => .node-22.13.1.pkg} | 0 ...{.tinygo-0.34.0.pkg => .tinygo-0.35.0.pkg} | 0 bin/corepack | 2 +- bin/firebase | 2 +- bin/gh | 2 +- bin/go | 2 +- bin/gofmt | 2 +- bin/golangci-lint | 2 +- bin/goreleaser | 2 +- bin/node | 2 +- bin/npm | 2 +- bin/npx | 2 +- bin/tinygo | 2 +- .../comment-hover-chromium-docker.png | Bin 93311 -> 95295 bytes .../comment-page-chromium-docker.png | Bin 72187 -> 73169 bytes .../dialog-chromium-docker.png | Bin 57654 -> 60131 bytes .../dialog-theme-chromium-docker.png | Bin 62238 -> 62914 bytes .../expand-0-chromium-docker.png | Bin 93739 -> 95705 bytes .../expand-1-chromium-docker.png | Bin 93320 -> 95238 bytes .../no-dialog-chromium-docker.png | Bin 74311 -> 76511 bytes .../printf-chromium-docker.png | Bin 90835 -> 93313 bytes .../printf-theme-chromium-docker.png | Bin 86813 -> 84794 bytes .../start-chromium-docker.png | Bin 74311 -> 76511 bytes .../start-theme-chromium-docker.png | Bin 71730 -> 69995 bytes e2e/package-lock.json | 26 +-- e2e/package.json | 4 +- .../console-output-chromium-docker.png | Bin 35250 -> 36450 bytes .../modal-chromium-docker.png | Bin 68541 -> 73457 bytes .../no-dialog-chromium-docker.png | Bin 29669 -> 30938 bytes .../no-sidebar-chromium-docker.png | Bin 29493 -> 30938 bytes .../read-input-chromium-docker.png | Bin 25003 -> 25944 bytes .../sidebar-chromium-docker.png | Bin 23082 -> 23673 bytes .../landing-top-chromium-docker.png | Bin 24830 -> 25155 bytes .../playground-chromium-docker.png | Bin 29669 -> 30927 bytes go.mod | 8 +- go.sum | 16 +- learn/go.mod | 10 +- learn/go.sum | 16 +- 46 files changed, 204 insertions(+), 121 deletions(-) docs: https://github.com/evylang/evy/blob/5b196cbe154c60d68b2c2deffa41e118985ffba9/docs/development/upgrade.md Pull-request: #461

juliaogris added 2 commits August 16, 2022 11:24

bin: Hermit install firebase

9e090e1

Hermit install firebase 11.6.0 with hermit install firebase

firebase: Initialise

8117645

Run `firebase init` and follow prompts with best intentions to avoid chaos 🤷‍♀️.

juliaogris force-pushed the firebase-init branch from 95e154f to 2ae3b46 Compare August 16, 2022 02:15

juliaogris force-pushed the firebase-init branch from 2ae3b46 to 03315e6 Compare August 16, 2022 02:18

camh- approved these changes Aug 16, 2022

View reviewed changes

juliaogris merged commit 6624fb8 into master Aug 16, 2022

juliaogris deleted the firebase-init branch August 16, 2022 02:23

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

firebase: Initialise firebase setup#2

firebase: Initialise firebase setup#2
juliaogris merged 3 commits intomasterfrom
firebase-init

juliaogris commented Aug 16, 2022 •

edited

Loading

Uh oh!

github-actions bot commented Aug 16, 2022 •

edited

Loading

Uh oh!

camh- left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

juliaogris commented Aug 16, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Aug 16, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

camh- left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

juliaogris commented Aug 16, 2022 •

edited

Loading

github-actions bot commented Aug 16, 2022 •

edited

Loading