4f21e40f73
This way 'npm publish' works and the package correctly has the resources in a '/package' directory inside the tarball. Tested by publishing locally, indeed the README is now correctly shown at https://www.npmjs.com/package/mastodon-bot/v/1.0.1-test-raboof-3 Will release 1.0.2 from master after merging
45 lines
844 B
Markdown
45 lines
844 B
Markdown
# Releasing
|
|
|
|
## dev release
|
|
```
|
|
shadow-cljs compile test
|
|
|
|
shadow-cljs release app
|
|
chmod a+x mastodon-bot.js
|
|
rm -rf target/npm-build
|
|
mkdir target/npm-build
|
|
cp mastodon-bot.js target/npm-build
|
|
cp package.json target/npm-build
|
|
cp README.md target/npm-build
|
|
|
|
npm publish ./target/npm-build --access public
|
|
```
|
|
|
|
## prod release (should be done from master)
|
|
```
|
|
shadow-cljs compile test
|
|
|
|
#adjust version
|
|
vi shadow-cljs.edn
|
|
|
|
git commit -am "releasing"
|
|
git tag [version]
|
|
git push && git push --tag
|
|
|
|
shadow-cljs release app
|
|
|
|
shadow-cljs release app
|
|
chmod a+x mastodon-bot.js
|
|
rm -rf target/npm-build
|
|
mkdir target/npm-build
|
|
cp mastodon-bot.js target/npm-build
|
|
cp package.json target/npm-build
|
|
cp README.md target/npm-build
|
|
|
|
npm publish ./target/npm-build --access public
|
|
|
|
# Bump version
|
|
vi shadow-cljs.edn
|
|
|
|
git commit -am "version bump" && git push
|
|
```
|