You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge branch 'feat/rsc-build' of github.com:dac09/redwood into feat/consolidate-vite-settings-rsc-builds
* 'feat/rsc-build' of github.com:dac09/redwood: (34 commits)
Add support for additional env var files (redwoodjs#9961)
Revert startsWith change
Remove outdated todo comment. And other comment formatting
no more 'as string', and startsWith instead of includes
innerText
Update studio.md (redwoodjs#10062)
doc comment formatting
node-loader should look in distRsc now, not distServer
Remove `serve` from test fixture
Code comment tweaks/fixes
Update some more comments
Remove duplicated file
Lint
Another rename of build functions
Fix paths test with new paths
Rename build functions
Tobbe review changes
Apply suggestions from code review
chore(rename): Be consistent with 'for' prefix for babel plugin option (redwoodjs#10059)
RSC: Remove commented code from worker (redwoodjs#10058)
...
Copy file name to clipboardexpand all lines: CHANGELOG.md
+51
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,57 @@
2
2
3
3
## Unreleased
4
4
5
+
- Add support for additional env var files (#9961)
6
+
7
+
Fixes #9877. This PR adds a new middleware step to the CLI that looks for an `--include-env-files` flag and includes `.env.[file]` to the list of dotfiles to load. This PR also introduces functionality so that `.env.[file]` files are loaded based on `NODE_ENV`.
These files are loaded in addition to `.env` and `.env.defaults` and more generally are additive. Subsequent dotfiles won't overwrite environment variables defined previous ones. As such, files loaded via NODE_ENV have lower priority than those loaded specifically via `--include-env-files`.
25
+
26
+
Note that this feature is mainly for local scripting. Most deploy providers don't let you upload dotfiles and usually have their own way of determining environments.
27
+
28
+
- fix(render): reduce memory and handle server file
29
+
30
+
This PR improves Render deploys by reducing memory consumption and fixing it so that it uses the server file if it's present.
31
+
32
+
Render deploys seems to consistently run out of memory during the data migration step. This step is configurable and its doubtful that every deploy has data migrations to apply, but it's enabled by default so it runs every time. The main issue is that the data migrate functionality is a plugin so a yarn install kicks off in Render's deploy container which must be more memory-constrained than the build container. (Assuming there are two different containers, which seems to be the case.)
33
+
34
+
Instead of running data migrations, this PR issues a warning that if you want to run data migrations, you need to first add the `@redwoodjs/cli-data-migrate` package as a devDependency:
35
+
36
+
```
37
+
yarn add -D @redwoodjs/cli-data-migrate
38
+
```
39
+
40
+
That way a `yarn install` won't be necessary to run data migrations.
41
+
42
+
Although this PR fixes Render deploy so that it uses the server file if present, realtime features still don't seem to work. We're still investigating; in the meantime, consider using another provider like Coherence if you're just getting started and want to try out realtime features.
43
+
44
+
- Update MetaTags to be Metadata in Docs (#10053)
45
+
46
+
The tutorial still used the `MetaTags` component instead of the newer `Metadata` component that the generator templates use. This PR updates all instances of `MetaTags` with `Metadata`.
47
+
48
+
## v7.0.2
49
+
50
+
- See https://github.com/redwoodjs/redwood/releases/tag/v7.0.2
51
+
52
+
## v7.0.1
53
+
54
+
- See https://github.com/redwoodjs/redwood/releases/tag/v7.0.1
55
+
5
56
## v7.0.0
6
57
7
58
- See https://github.com/redwoodjs/redwood/releases/tag/v7.0.0 for the release notes and https://community.redwoodjs.com/t/redwood-v7-0-0-upgrade-guide/5713 for the upgrade guide
Copy file name to clipboardexpand all lines: docs/docs/studio.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ RedwoodJS Studio is a package used during development to gain runtime insights i
10
10
11
11
Redwood provides tools that lets developers "get to work on what makes your application special, instead of wasting cycles choosing and re-choosing various technologies and configurations."[1](https://github.com/redwoodjs/redwood/blob/main/README.md).
12
12
13
-
Much happens while your app processes a request: Invoke a function; handle a GraphQL request; resolve the request with a service; build and execute a SQL statement; connect to the database; handle the query response; further resolve the response so in contains all the data needed; return the result ... and more.
13
+
Much happens while your app processes a request: Invoke a function; handle a GraphQL request; resolve the request with a service; build and execute a SQL statement; connect to the database; handle the query response; further resolve the response so it contains all the data needed; return the result ... and more.
14
14
15
15
While [logging](https://redwoodjs.com/docs/logger) can show you some of these steps, there is no easy way to see how they relate to each other, compare, or break down individual timings. Observability needed to debug, iterate, try out, and refactor your code is lacking.
0 commit comments