@merkur/cli 0.44.0-rc.5 → 0.44.0
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/README.md +4 -0
- package/bin/merkur.mjs +1 -1
- package/package.json +3 -3
- package/src/commands/buildPlayground.mjs +1 -1
package/README.md
CHANGED
|
@@ -40,6 +40,7 @@ Contribute to this project via [Pull-Requests](https://github.com/mjancarik/merk
|
|
|
40
40
|
|
|
41
41
|
We are following [Conventional Commits Specification](https://www.conventionalcommits.org/en/v1.0.0/#summary). To simplify the commit process, you can use `npm run commit` command. It opens an interactive interface, which should help you with commit message composition.
|
|
42
42
|
|
|
43
|
+
|
|
43
44
|
### Release
|
|
44
45
|
|
|
45
46
|
To release a version you must have the right permissions, please contact one of the repo maintainers.
|
|
@@ -60,6 +61,7 @@ npm run release
|
|
|
60
61
|
npx lerna version <preminor | prepatch | prerelease> --no-git-tag-version --no-push
|
|
61
62
|
// prerelease increments the pre* version's last number, e.g. v0.44.0-rc.0 => v0.44.0-rc.1
|
|
62
63
|
```
|
|
64
|
+
- alternatively, manually change the version in the package's `package.json` and in `lerna.json`, and run `npm install` from the root of the monorepo.
|
|
63
65
|
2. Restore all files not related to the package you intend to release. These files should remain:
|
|
64
66
|
- the package's own `package.json`
|
|
65
67
|
- `lerna.json` (otherwise lerna will stop incrementing the pre-version's number, for some reason)
|
|
@@ -71,6 +73,8 @@ npm run release
|
|
|
71
73
|
|
|
72
74
|
The packages are released from a GitHub Action that is triggered when a new version tag is pushed to the repository.
|
|
73
75
|
|
|
76
|
+
Before the actual release, it's safer to return all version numbers to the last stable version. Another option is to release from a separate branch, so your feature branch stays clean.
|
|
77
|
+
|
|
74
78
|
---
|
|
75
79
|
|
|
76
80
|
Thank you to all the people who already contributed to Merkur!
|
package/bin/merkur.mjs
CHANGED
|
@@ -116,7 +116,7 @@ program
|
|
|
116
116
|
...cmd.optsWithGlobals(),
|
|
117
117
|
...options,
|
|
118
118
|
};
|
|
119
|
-
process.env.NODE_ENV = process.env.NODE_ENV ?? '
|
|
119
|
+
process.env.NODE_ENV = process.env.NODE_ENV ?? 'development';
|
|
120
120
|
|
|
121
121
|
await buildPlayground({ args, command: COMMAND_NAME.BUILD_PLAYGROUND });
|
|
122
122
|
});
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@merkur/cli",
|
|
3
|
-
"version": "0.44.0
|
|
3
|
+
"version": "0.44.0",
|
|
4
4
|
"description": "Merkur is tiny and extensible library for creating front-end microservices.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"merkur": "./bin/merkur.mjs"
|
|
@@ -60,11 +60,11 @@
|
|
|
60
60
|
"ws": "^8.18.3"
|
|
61
61
|
},
|
|
62
62
|
"devDependencies": {
|
|
63
|
-
"@merkur/core": "^0.
|
|
63
|
+
"@merkur/core": "^0.44.0",
|
|
64
64
|
"@types/express": "^5.0.4"
|
|
65
65
|
},
|
|
66
66
|
"engines": {
|
|
67
67
|
"node": ">=20"
|
|
68
68
|
},
|
|
69
|
-
"gitHead": "
|
|
69
|
+
"gitHead": "34a84c97b1e3ae060ec947b90c5a3ccb98b83362"
|
|
70
70
|
}
|
|
@@ -134,7 +134,7 @@ export async function buildPlayground({ args, command }) {
|
|
|
134
134
|
} else {
|
|
135
135
|
const isRegeExp = playground?.path?.constructor?.name === 'RegExp';
|
|
136
136
|
logger.warn(
|
|
137
|
-
`Static build requires a string playground path, but your path is ${isRegeExp ? 'a RegExp' : 'undefined'}. Using '/' as fallback; you can set the path
|
|
137
|
+
`Static build requires a string playground path, but your path is ${isRegeExp ? 'a RegExp' : 'undefined'}. Using '/' as fallback; you can set the path through the --playgroundPath CLI option.`,
|
|
138
138
|
);
|
|
139
139
|
playgroundPath = '/';
|
|
140
140
|
}
|