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
and everything was like expected. Today I ran setup again (to regenerate package-lock.json in an interactive rebase)
$ npx typia setup
Need to install the following packages:
typia@5.1.3
Ok to proceed? (y) y
----------------------------------------
Typia Setup Wizard
----------------------------------------
? Package Manager npm
npm install --save-dev ts-patch@latest
npm install --save-dev ts-node@latest
npm install --save-dev typescript@4.9.5
npm run postinstall
and suddenly the typescript version is downgraded. Is this expected?
Looking into all commits (git reflog -p -G typia -- package.json | grep typia | sort -u, same for package-lock.json), the version installed has always been 5.1.3, so it is not that I used to have 5.0.5 and then updated.
And since currently there are no commits present after the 5.1.3 release (which was done earlier yesterday) there are no logical explanation for the difference in behaviour.
The text was updated successfully, but these errors were encountered:
Question
Yesterday I ran setup
$ npx typia setup ---------------------------------------- Typia Setup Wizard ---------------------------------------- ? Package Manager npm npm install --save-dev ts-patch@latest npm install --save-dev ts-node@latest npm install --save-dev typescript@latest npm run postinstall $
and everything was like expected. Today I ran setup again (to regenerate
package-lock.json
in an interactive rebase)and suddenly the typescript version is downgraded. Is this expected?
Looking into all commits (
git reflog -p -G typia -- package.json | grep typia | sort -u
, same forpackage-lock.json
), the version installed has always been 5.1.3, so it is not that I used to have 5.0.5 and then updated.And since currently there are no commits present after the 5.1.3 release (which was done earlier yesterday) there are no logical explanation for the difference in behaviour.
The text was updated successfully, but these errors were encountered: