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
Currently, we are using read-pkg-up to load module version at run time.
There has a discussion between @footballencarta and me before, at huan/rx-queue#25 (comment), I agree with most of his options and I decide to generate a static for our modules to prevent some strange bugs.
The most recent bug I had experienced is that the read-pkg-up package API had a breaking change, which causes a log problem in our Chatie ecosystem because I'm heavy depended on it.
So what I'm planning to do, is:
Create a dummy src/version.ts file only export const VERSION = '0.0.0'
Add a unit test to make sure the VERSION exported from version.ts is equal to 0.0.0
Add a scripts/generate-version.ts to generate src/version.ts file
Run scripts/generate-version.ts right before npm run dist in Travis CI
So that we can save the version number to our module before npm publish
The text was updated successfully, but these errors were encountered:
Currently, we are using read-pkg-up to load module version at run time.
There has a discussion between @footballencarta and me before, at huan/rx-queue#25 (comment), I agree with most of his options and I decide to generate a static for our modules to prevent some strange bugs.
The most recent bug I had experienced is that the
read-pkg-up
package API had a breaking change, which causes a log problem in our Chatie ecosystem because I'm heavy depended on it.So what I'm planning to do, is:
src/version.ts
file onlyexport const VERSION = '0.0.0'
VERSION
exported fromversion.ts
is equal to0.0.0
scripts/generate-version.ts
to generatesrc/version.ts
filescripts/generate-version.ts
right beforenpm run dist
in Travis CInpm publish
The text was updated successfully, but these errors were encountered: