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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@cloudflare/[email protected]
Minor Changes
#9914
a24c9d8Thanks @petebacondarwin! - Add support for loading local dev vars from .env filesIf there are no
.dev.varsor.dev.vars.<environment>files, when running Wrangler or the Vite plugin in local development mode,they will now try to load additional local dev vars from
.env,.env.local,.env.<environment>and.env.<environment>.localfiles.These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker.
Wrangler and Vite will continue to load
.envfiles in order to configure themselves as a tool.Further details:
vite buildthe local vars will be computed and stored in a.dev.varsfile next to the compiled Worker code, so thatvite previewcan use them.wrangler typescommand will similarly read the.envfiles (if no.dev.varsfiles) in order to generate theEnvinterface.CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENVenvironment variable is"false"then local dev variables will not be loaded from.envfiles.CLOUDFLARE_INCLUDE_PROCESS_ENVenvironment variable is"true"then all the environment variables found onprocess.envwill be included as local dev vars.--env-file=<path/to/dotenv/file>global CLI option. This affects both loading.envto configure Wrangler the tool as well as loading local dev vars.Patch Changes
#10071
4a4049cThanks @CarmenPopoviciu! - feat(vite-plugin): Add Containers-related info logsAdd logs, when a Worker has Containers configured, providing information about container build status, and how to rebuild containers during local development.
Updated dependencies [
9b61f44,0f7820e,a24c9d8,e9bb8d3]:[email protected]
Minor Changes
#9914
a24c9d8Thanks @petebacondarwin! - Add support for loading local dev vars from .env filesIf there are no
.dev.varsor.dev.vars.<environment>files, when running Wrangler or the Vite plugin in local development mode,they will now try to load additional local dev vars from
.env,.env.local,.env.<environment>and.env.<environment>.localfiles.These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker.
Wrangler and Vite will continue to load
.envfiles in order to configure themselves as a tool.Further details:
vite buildthe local vars will be computed and stored in a.dev.varsfile next to the compiled Worker code, so thatvite previewcan use them.wrangler typescommand will similarly read the.envfiles (if no.dev.varsfiles) in order to generate theEnvinterface.CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENVenvironment variable is"false"then local dev variables will not be loaded from.envfiles.CLOUDFLARE_INCLUDE_PROCESS_ENVenvironment variable is"true"then all the environment variables found onprocess.envwill be included as local dev vars.--env-file=<path/to/dotenv/file>global CLI option. This affects both loading.envto configure Wrangler the tool as well as loading local dev vars.Patch Changes
#10051
0f7820eThanks @nikitassharma! - Add support for custom instance limits for containers. For example, instead ofhaving to use the preconfigured dev/standard/basic instance types, you can now
set:
This feature is currently only available to customers on an enterprise plan.
#10149
e9bb8d3Thanks @vicb! - fixrequire("debug")in nodejs_compat modeUpdated dependencies [
9b61f44]:[email protected]
Patch Changes
#10109
d983f2bThanks @alan-agius4! - chore: update dependencies of "create-cloudflare" packageThe following dependency versions have been updated:
[email protected]
Patch Changes
#10129
9b61f44Thanks @dependabot! - chore: update dependencies of "miniflare" packageThe following dependency versions have been updated:
@cloudflare/[email protected]
Patch Changes
9b61f44]:@cloudflare/[email protected]
Patch Changes
9b61f44,0f7820e,a24c9d8,e9bb8d3]: