@aion0/forge 0.9.5 → 0.9.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/RELEASE_NOTES.md +3 -3
- package/bin/forge-server.mjs +6 -1
- package/package.json +1 -1
package/RELEASE_NOTES.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
|
-
# Forge v0.9.
|
|
1
|
+
# Forge v0.9.6
|
|
2
2
|
|
|
3
3
|
Released: 2026-05-26
|
|
4
4
|
|
|
5
|
-
## Changes since v0.9.
|
|
5
|
+
## Changes since v0.9.5
|
|
6
6
|
|
|
7
7
|
|
|
8
|
-
**Full Changelog**: https://github.com/aiwatching/forge/compare/v0.9.
|
|
8
|
+
**Full Changelog**: https://github.com/aiwatching/forge/compare/v0.9.5...v0.9.6
|
package/bin/forge-server.mjs
CHANGED
|
@@ -33,7 +33,12 @@ function buildNext() {
|
|
|
33
33
|
// Check if devDependencies are installed (e.g. @tailwindcss/postcss)
|
|
34
34
|
if (!existsSync(join(ROOT, 'node_modules', '@tailwindcss', 'postcss'))) {
|
|
35
35
|
console.log('[forge] Installing dependencies...');
|
|
36
|
-
|
|
36
|
+
// --legacy-peer-deps: next-auth@5-beta + its nested @auth/core declare
|
|
37
|
+
// contradictory peerOptional nodemailer requirements (v7 vs v6) — both
|
|
38
|
+
// optional, but npm 10+ treats this as a hard ERESOLVE error. Same
|
|
39
|
+
// policy as the repo's .npmrc, baked in here so it works even in the
|
|
40
|
+
// installed npm-package copy (.npmrc isn't published).
|
|
41
|
+
execSync('npm install --include=dev --legacy-peer-deps', { cwd: ROOT, stdio: 'inherit' });
|
|
37
42
|
}
|
|
38
43
|
execSync('npx next build', { cwd: ROOT, stdio: 'inherit', env: { ...process.env } });
|
|
39
44
|
}
|