Commit graph

34 commits

Author SHA1 Message Date
dmitri.sotnikov@gmail.com
6bd61ccd2f bumped up version 2020-12-29 17:09:39 -05:00
dmitri.sotnikov@gmail.com
10cdbb0a7e 1.10.1 2020-11-22 18:46:22 -05:00
dmitri.sotnikov@gmail.com
1658e4fb00 fixed package.json 2020-11-22 18:41:21 -05:00
dmitri.sotnikov@gmail.com
330d9739c2 1.10.0 2020-11-22 18:30:11 -05:00
Dmitri Sotnikov
adfef0e663
updated repository url 2020-11-22 18:26:13 -05:00
jem
e4cd6f2f2f configuring the npm reg - but unsure about the url to use. 2020-11-09 08:31:11 +01:00
jem
8df1214255 releasing 2020-11-06 19:17:04 +01:00
jem
2a37e55158 releasing 2020-11-06 19:05:37 +01:00
jem
2feca1f23e version bump 2020-11-06 18:32:43 +01:00
jem
9b688a23cb releasing 2020-11-06 18:28:29 +01:00
dmitri.sotnikov@gmail.com
5414e01048 releasing 2020-11-06 11:41:59 -05:00
Dmitri Sotnikov
03a4c950cf
update deasync to 0.1.20 2020-11-03 16:16:28 -05:00
dmitri.sotnikov@gmail.com
96ececd255 bumped up version 2020-07-11 10:10:40 -04:00
dmitri.sotnikov@gmail.com
e7b0ed233e bumped up package.json version 2020-07-09 14:44:35 -04:00
Arnout Engelen
4f21e40f73
Publish the target directory without creating our own tarball
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
2020-07-09 16:42:11 +02:00
dmitri.sotnikov@gmail.com
5f23a98920 bumped up package.json version 2020-06-29 15:15:17 -04:00
jem
57376d2e15 increase version for improved release publishing ci 2020-06-29 19:55:28 +02:00
dmitri.sotnikov@gmail.com
27c99a7d55 bumped up version for release 2020-06-29 13:06:25 -04:00
jem
b231fc5209 works :-) 2020-06-29 18:47:55 +02:00
jem
09046c0dee next try to publish 2020-06-26 18:01:26 +02:00
jem
49fe78dc06 prepare for publishing on npm 2020-06-26 10:42:32 +02:00
jem
ceaf1a2034 maybe files have also to be adjusted in package.json? 2020-06-09 08:22:12 +02:00
jem
64cea0fea7 fix package.json 2020-06-09 08:08:55 +02:00
Arnout Engelen
9c80c4cab0
Release 0.0.2 2020-05-07 09:15:52 +02:00
Arnout Engelen
7f992e9d73
Add filters so 'npm pack' and publish contains just enough 2020-04-14 15:40:57 +02:00
Arnout Engelen
043f1e0fd3 Remove separate main.cljs, install to PATH
https://docs.npmjs.com/files/package.json#bin
2020-03-19 09:56:11 +01:00
dmitri.sotnikov@gmail.com
820cd2be82 added shadow-cljs compilation to generate a js artifact 2020-02-27 20:23:48 -05:00
Arnout Engelen
ea7c057c11 Add a unit test
Splitting up the project in core/main/test
2020-02-27 13:20:11 +01:00
dmitri.sotnikov@gmail.com
d79b9fa5c3 bumped up dependencies 2019-06-28 09:21:14 -04:00
Dmitri Sotnikov
8c004bd876 switched to use request module instead of curl to resolve urls 2018-08-28 02:18:01 -04:00
dmitri.sotnikov@gmail.com
1f411891a8 added RSS support 2018-03-20 08:57:25 -04:00
dmitri.sotnikov@gmail.com
f67f55c858 added tumblr support 2018-03-15 09:23:27 -04:00
AJ Jordan
8bf710dd61
Declare Lumo as a dependency
This means that we always have the right version, regardless of what's
in the global environment. Note that npm scripts (including `npm
start`) automatically prepend `./node_modules/.bin` to $PATH, which is
how this works.

See also http://module.party
2018-03-14 14:21:54 -04:00
dmitri.sotnikov@gmail.com
75b679a533 initial commit 2018-03-14 09:50:34 -04:00