Is your request related to a problem?
When installing & using an older version of MarkBind (e.g. by npm i markbind-cli@3.1.0), the current configuration will install the referenced MarkBind core packages with version v3.1.1 instead, because they are compatible. This means the site that is built from markbind-cli@3.1.0 will have the version specified as v3.1.1, and it supports functionalities added in v3.1.1.
Thus, it becomes almost impossible for a user to specify an exact MarkBind version to use.
Describe the solution you'd like
With reference to the npm docs, use exact version number instead of a range.
E.g. in packages/cli/package.json
"@markbind/core": "^3.1.1",
"@markbind/core-web": "^3.1.1",
should be
"@markbind/core": "3.1.1",
"@markbind/core-web": "3.1.1",
Additional context
#1839 (comment) and the subsequent comments
Is your request related to a problem?
When installing & using an older version of MarkBind (e.g. by npm i markbind-cli@3.1.0), the current configuration will install the referenced MarkBind core packages with version v3.1.1 instead, because they are compatible. This means the site that is built from markbind-cli@3.1.0 will have the version specified as v3.1.1, and it supports functionalities added in v3.1.1.
Thus, it becomes almost impossible for a user to specify an exact MarkBind version to use.
Describe the solution you'd like
With reference to the npm docs, use exact version number instead of a range.
E.g. in packages/cli/package.json
should be
Additional context
#1839 (comment) and the subsequent comments