Skip to content
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

ZEA-4175: Handle the containerized mode of Node.js output directory #376

Conversation

pan93412
Copy link
Member

@pan93412 pan93412 commented Nov 5, 2024

Description (required)

  • fix(planner/nodejs): Make build script determination reliable
  • refactor(planner/gleam): Optimize serverless generation
  • feat(planner/nodejs): Support containerized outputDir generation
  • feat(planner/nodejs): Support containerized static
  • feat(zbpack): Support new containerized static convention
  • feat(planner/dart): Support containerized static
  • fix(planner/nodejs): Do not fill start command if there is static output directory
  • test(transformer): Update for latest serverless + outputDir convention
  • test(e2e): Add vite vanilla test
  • chore: Update dependencies
  • ci: Use go-version-file for release

Node.js and Flutter has been manually tested.

Related issues & labels (optional)

  • Closes ZEA-4175
  • Suggested label: enhancement, bug

@pan93412 pan93412 self-assigned this Nov 5, 2024
@pan93412 pan93412 marked this pull request as draft November 5, 2024 10:29
@pan93412 pan93412 marked this pull request as ready for review November 5, 2024 10:31
@pan93412 pan93412 marked this pull request as draft November 5, 2024 10:32
@pan93412 pan93412 marked this pull request as ready for review November 5, 2024 10:44
@yuaanlin yuaanlin merged commit 3487729 into main Nov 7, 2024
5 checks passed
@yuaanlin yuaanlin deleted the pan93412/zea-4175-handle-the-containerized-mode-of-nodejs-outputdir branch November 7, 2024 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants