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
Enable all webpack sourcemaps in dev build, disable all in prod build (#25089)
- Enable all source maps in dev build
- Disable all source maps in prod build
- Provide `ENABLE_SOURCEMAP` env var to override it.
I think the strange error seen in
#24784 is sourcemap related, so
if we enable/disable them all, it might go away. But it's most
definitely a Safari bug.
With all sourcemaps disabled, binary size goes down by around 1-2 MB,
with all enabled it goes up by around 12MB. If +12MB is acceptable, we
could also always enable them by default as fully source maps do have
some debugging benefits.
Copy file name to clipboardexpand all lines: docs/content/doc/installation/from-source.en-us.md
+2
Original file line number
Diff line number
Diff line change
@@ -132,6 +132,8 @@ If pre-built frontend files are present it is possible to only build the backend
132
132
TAGS="bindata" make backend
133
133
```
134
134
135
+
Webpack source maps are by default enabled in development builds and disabled in production builds. They can be enabled by setting the `ENABLE_SOURCEMAP=true` environment variable.
136
+
135
137
## Test
136
138
137
139
After following the steps above, a `gitea` binary will be available in the working directory.
0 commit comments