feat(lagon): write Lagon config on build #996
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
#966
β Type of change
π Description
Since
@lagon/cli@0.5.0
, Lagon supports configuration files (https://github.com/lagonapp/lagon/releases/tag/%40lagon%2Fcli%400.5.0)This PR outputs Lagon's configuration file when the build is complete. It's written inside
${output.dir}/.lagon/config.json
(e.g.output/.lagon/config.json
) and allows to start the dev server / deploy the function without specifying the function's entry point (server/index.mjs
) and the public directory (public
) manually.Notes:
.lagon
folderfunction_id
&organization_id
fields are empty, they are used to detect if the function has been deployed or notclient
field is a path to a client-side JS script that can be bundled and injected into the assets, but is useless for Nitro.π Checklist