3wordchant/oasis
0
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
2262116d08
oasis/package.json

121 lines
3.4 KiB
JSON
Raw Normal View History

.
2019-06-21 16:18:19 +00:00
{
Change name to publish with bin script
2019-06-24 19:26:29 +00:00
"name": "@fraction/oasis",
2.16.0
2020-04-13 21:32:21 +00:00
"version": "2.16.0",
Change to make Sharp an optional dependency
2019-12-28 00:28:36 +00:00
"description": "friendly neighborhood scuttlebutt interface",
Make Travis faster by removing double-build Problem: Travis builds PRs and branches, which means that local branches get built twice (!). Solution: Travis should only build `master`, and maybe tags.
2020-01-23 20:09:54 +00:00
"repository": {
"type": "git",
"url": "git+ssh://git@github.com/fraction/oasis.git"
},
Add reply-all feature for non-forky replies
2019-09-27 00:19:18 +00:00
"license": "AGPL-3.0",
Change to make Sharp an optional dependency
2019-12-28 00:28:36 +00:00
"author": "Christian Bundy <christianbundy@fraction.io>",
Change src directory to use mediator pattern
2020-01-08 16:37:52 +00:00
"main": "src/index.js",
Change to make Sharp an optional dependency
2019-12-28 00:28:36 +00:00
"bin": {
Make Travis faster by removing double-build Problem: Travis builds PRs and branches, which means that local branches get built twice (!). Solution: Travis should only build `master`, and maybe tags.
2020-01-23 20:09:54 +00:00
"oasis": "src/index.js"
Change to make Sharp an optional dependency
2019-12-28 00:28:36 +00:00
},
"scripts": {
Change src directory to use mediator pattern
2020-01-08 16:37:52 +00:00
"dev": "nodemon --inspect src/index.js --debug --no-open",
Experiment with common-good module
2020-01-22 00:22:19 +00:00
"fix": "common-good fix",
Change src directory to use mediator pattern
2020-01-08 16:37:52 +00:00
"start": "node src/index.js",
restore common-good check & fix its errors after having restored the package-lock.json to that of the master branch, this PR now uses common-good@2.0.3, which has common-good check as a command. i ran it manually as $(npm bin)/common-good check, and fixed whatever it complained about.
2020-10-21 13:33:01 +00:00
"test": "tap --timeout 240 && common-good check --dependency-check-suffix '-i changelog-version -i mkdirp -i nodemon -i stylelint-config-recommended'",
Add latest changes to changelog
2020-01-16 19:53:01 +00:00
"preversion": "npm test",
Fix broken changelog moving logic Problem: The `npm version` command is supposed to do some changelog magic but the paths are broken. Solution: Use the correct paths.
2020-04-10 19:48:02 +00:00
"version": "mv docs/CHANGELOG.md ./ && changelog-version && mv CHANGELOG.md docs/ && git add docs/CHANGELOG.md"
Change to make Sharp an optional dependency
2019-12-28 00:28:36 +00:00
},
.
2019-06-21 16:18:19 +00:00
"dependencies": {
Change to use new API from `@fraction/base16-css`
2019-10-16 04:00:03 +00:00
"@fraction/base16-css": "^1.1.0",
Update npm dependencies Problem: Our dependencies are falling behind and it'd be nice to have them up-to-date. The only big update it that Common-Good upgraded to the latest version of Prettier. Solution: Update them!
2020-03-23 22:54:28 +00:00
"@koa/router": "^8.0.0",
Add nested replies to thread view
2019-06-28 20:55:05 +00:00
"debug": "^4.1.1",
Read settings from ~/.config/oasis/config.json This should give pretty much expected behaviour. Each config value can be set by three sources: 1. By command-line argument. If it is not given, then 2. By config file. Or, lastly 3. By default value in the source code. I can't test that the config file is searched and read from the right place on windows or macOS, but on linux it works.
2020-02-22 00:59:51 +00:00
"env-paths": "^2.2.0",
Bump file-type from 15.0.1 to 16.0.1 Bumps [file-type](https://github.com/sindresorhus/file-type) from 15.0.1 to 16.0.1. - [Release notes](https://github.com/sindresorhus/file-type/releases) - [Commits](https://github.com/sindresorhus/file-type/compare/v15.0.1...v16.0.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 01:11:13 +00:00
"file-type": "^16.0.1",
Bump highlight.js from 9.18.1 to 10.4.0 Bumps [highlight.js](https://github.com/highlightjs/highlight.js) from 9.18.1 to 10.4.0. - [Release notes](https://github.com/highlightjs/highlight.js/releases) - [Changelog](https://github.com/highlightjs/highlight.js/blob/master/CHANGES.md) - [Commits](https://github.com/highlightjs/highlight.js/compare/9.18.1...10.4.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:59:07 +00:00
"highlight.js": "^10.4.0",
Refactor to use hyperaxe instead of EJS
2019-06-27 20:36:43 +00:00
"hyperaxe": "^1.3.0",
Fix SVG rendering by setting content-type Problem: Most browsers parse SVG files as XML and refuse to display it in an `<img>` tag. It's usually unsafe to have browsers try to sniff the file type themselves, because they can be tricked into running unsafe code, so we want to set the file type ourselves in the server. Solution: Use the Is-SVG library for a quick-n-dirty check for whether a buffer is an SVG. If so, we set the file type accordingly.
2020-01-31 23:04:13 +00:00
"is-svg": "^4.2.1",
Initial commit
2019-06-23 18:46:22 +00:00
"koa": "^2.7.0",
Add unliking
2019-06-26 00:53:12 +00:00
"koa-body": "^4.1.0",
Add syntax highlighting
2019-06-25 16:52:34 +00:00
"koa-mount": "^4.0.0",
Refactor to use smaller and better-organized components
2019-06-25 03:10:13 +00:00
"koa-static": "^5.0.0",
Initial commit
2019-06-23 18:46:22 +00:00
"lodash": "^4.17.11",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"lodash.shuffle": "^4.2.0",
Bump markdown-it from 10.0.0 to 12.0.2 Bumps [markdown-it](https://github.com/markdown-it/markdown-it) from 10.0.0 to 12.0.2. - [Release notes](https://github.com/markdown-it/markdown-it/releases) - [Changelog](https://github.com/markdown-it/markdown-it/blob/master/CHANGELOG.md) - [Commits](https://github.com/markdown-it/markdown-it/compare/10.0.0...12.0.2) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:20:09 +00:00
"markdown-it": "^12.0.2",
Update npm dependencies Problem: Our dependencies are falling behind and it'd be nice to have them up-to-date. The only big update it that Common-Good upgraded to the latest version of Prettier. Solution: Update them!
2020-03-23 22:54:28 +00:00
"open": "^7.0.3",
remove exif data from uploaded jpegs
2020-10-14 12:38:00 +00:00
"piexifjs": "^1.0.4",
Bump pretty-ms from 6.0.1 to 7.0.1 Bumps [pretty-ms](https://github.com/sindresorhus/pretty-ms) from 6.0.1 to 7.0.1. - [Release notes](https://github.com/sindresorhus/pretty-ms/releases) - [Commits](https://github.com/sindresorhus/pretty-ms/compare/v6.0.1...v7.0.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 01:00:09 +00:00
"pretty-ms": "^7.0.1",
Fix tests and remove workaround Problem: Recently there was a PR [0] merged with a quickfix to avoid some test failures, which is something I've been trying to avoid. While `process.exit()` works fine, I'm worried that it means we don't understand what's happening under the hood, *plus* I have the [maybe unjustified?] worry that it might kill the process during a database write or something dangerous. It looks like this particular test hang was caused by both a stream and some number of intervals that were left open. Solution: Provide a way to close the stream and intervals in `index.js` and ensure that we do that before closing the server. [0]: https://github.com/fraction/oasis/pull/462
2020-11-11 16:25:16 +00:00
"pull-abortable": "^4.1.1",
Use pull-paramap to speed up like page
2019-10-01 00:46:04 +00:00
"pull-paramap": "^1.2.2",
Replace dog-food filter with popular page Instead of trying to remove ssb-dev content explicitly I'm going to try to experiment with a "popular" page that count all of the votes in the past 24 hours and shows the posts with the most votes.
2019-12-06 19:31:35 +00:00
"pull-sort": "^1.0.2",
Initial commit
2019-06-23 18:46:22 +00:00
"pull-stream": "^3.6.12",
Fix syntax highlighter with require-style
2019-06-29 19:56:59 +00:00
"require-style": "^1.1.0",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"secret-stack": "^6.3.0",
Bump sharp from 0.25.2 to 0.26.3 Bumps [sharp](https://github.com/lovell/sharp) from 0.25.2 to 0.26.3. - [Release notes](https://github.com/lovell/sharp/releases) - [Changelog](https://github.com/lovell/sharp/blob/master/docs/changelog.md) - [Commits](https://github.com/lovell/sharp/compare/v0.25.2...v0.26.3) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:32:20 +00:00
"sharp": "^0.26.3",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"ssb-about": "^2.0.1",
Bump ssb-backlinks from 1.0.0 to 2.1.1 Bumps [ssb-backlinks](https://github.com/ssbc/ssb-backlinks) from 1.0.0 to 2.1.1. - [Release notes](https://github.com/ssbc/ssb-backlinks/releases) - [Commits](https://github.com/ssbc/ssb-backlinks/commits/v2.1.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 20:26:09 +00:00
"ssb-backlinks": "^2.1.1",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"ssb-blobs": "^1.2.2",
Replace cooler methods with SSB-Client promises Problem: We started using `cooler.get()` and `cooler.read()` because it was impossible to use promises with SSB-Client. Solution: I made some downstream pull requests into the MuxRPC module and the SSB-Client module, which means that both of them now natively support promises. This commit removes the weird convenience methods and replaces them with the native promise support, which should hopefully make the code easier to read and write.
2020-02-11 20:48:50 +00:00
"ssb-client": "^4.9.0",
"ssb-config": "^3.4.4",
Bump ssb-conn from 0.17.0 to 0.19.1 Bumps [ssb-conn](https://github.com/staltz/ssb-conn) from 0.17.0 to 0.19.1. - [Release notes](https://github.com/staltz/ssb-conn/releases) - [Commits](https://github.com/staltz/ssb-conn/compare/v0.17.0...v0.19.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 20:25:07 +00:00
"ssb-conn": "^0.19.1",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"ssb-db": "^19.4.0",
"ssb-ebt": "^5.6.7",
"ssb-friends": "^4.1.4",
"ssb-invite": "^2.1.3",
Add more comprehensive tests Problem: I've been worried about merging these version bump pull requests since we don't have many tests, and I *really* don't want to merge any catostrophic breaking changes anywhere. Solution: Add some tests that are more comprehensive, starting by creating a temporary SSB database and keypair and then editing the profile, previewing a message, publishing a message, etc., until we have a handful of small functions actually being tested. This won't ensure that everything works forever, and it *really* doesn't test replication, but it should help increase our confidence that test success means that fewer things are broken.
2020-11-22 23:35:15 +00:00
"ssb-keys": "^8.0.0",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"ssb-lan": "^0.2.0",
"ssb-logging": "^1.0.0",
Update npm dependencies Problem: Our dependencies are getting ahead of us! Solution: Catch up with `npm update`. I think Markdown-It was the only breaking change, and it didn't affect us.
2020-04-03 14:11:11 +00:00
"ssb-markdown": "^6.0.7",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"ssb-master": "^1.0.3",
"ssb-meme": "^1.0.4",
Update SSB-Mentions and remove workaround Problem: We've been using a workaround to filter the results of SSB-Mentions, but that's just been fixed upstream and so we don't need the workaround anymore. Solution: Update the SSB-Mentions package and remove the workaround.
2020-02-19 22:35:40 +00:00
"ssb-mentions": "^0.5.2",
Fix ssb-msgs broken from mechanical edit
2019-06-27 22:07:09 +00:00
"ssb-msgs": "^5.2.0",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"ssb-no-auth": "^1.0.0",
"ssb-onion": "^1.0.0",
"ssb-ooo": "^1.3.1",
"ssb-plugins": "^1.0.2",
"ssb-query": "^2.4.3",
Add standalone support if ssb-client can't connect
2019-06-28 16:13:35 +00:00
"ssb-ref": "^2.13.9",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"ssb-replicate": "^1.3.0",
"ssb-room": "^1.2.2",
"ssb-search": "^1.2.1",
Fix tangle bug when Patchwork is used as a server Problem: Patchwork is missing a plugin that we need to set the `branch` property when posting a message. This property is important because it helps us sort threads, so we're throwing an error when it isn't available. See: https://github.com/fraction/oasis/issues/21 Solution: HACK THE ~~PLANET~~ API. This commit injects the plugin we need via Oasis, which is a bit of a duct tape solution but it *is* a solution.
2020-01-26 20:54:56 +00:00
"ssb-tangle": "^1.0.1",
Change to update all dependencies
2019-11-13 04:48:37 +00:00
"ssb-thread-schema": "^1.1.1",
Merge flotilla source code into Oasis Problem: I thought it would be a good idea to keep our SSB stack in another module but it just creates friction and adds another layer to our stack that has to be independently upgraded and versioned. Solution: Merge the @fraction/flotilla source code into Oasis so that we don't have to maintain two separate projects.
2020-11-22 18:06:35 +00:00
"ssb-unix-socket": "^1.0.0",
"ssb-ws": "^6.2.3",
Bump yargs from 15.3.1 to 16.1.1 Bumps [yargs](https://github.com/yargs/yargs) from 15.3.1 to 16.1.1. - [Release notes](https://github.com/yargs/yargs/releases) - [Changelog](https://github.com/yargs/yargs/blob/master/CHANGELOG.md) - [Commits](https://github.com/yargs/yargs/compare/v15.3.1...v16.1.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:18:42 +00:00
"yargs": "^16.1.1"
Change license to ISC, add description to package.json
2019-06-24 19:13:16 +00:00
},
Change rendering engine to use ejs instead of swig
2019-06-24 22:00:10 +00:00
"devDependencies": {
Add TypeScript definitions for better guardrails Problem: We have TypeScript enabled on the project but have been missing lots of definition files, so there are like 500 errors when you enable `--noImplicitAny`. Solution: Add definitions and fix the bugs that they point out. This reduces the number of errors with `--noImplicitAny` to 285.
2020-03-24 16:21:59 +00:00
"@types/debug": "^4.1.5",
Bump @types/highlight.js from 9.12.3 to 10.1.0 Bumps [@types/highlight.js](https://github.com/highlightjs/highlight.js) from 9.12.3 to 10.1.0. - [Release notes](https://github.com/highlightjs/highlight.js/releases) - [Changelog](https://github.com/highlightjs/highlight.js/blob/master/CHANGES.md) - [Commits](https://github.com/highlightjs/highlight.js/commits/10.1.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:31:57 +00:00
"@types/highlight.js": "^10.1.0",
Remove @ts-ignore workaround Problem: The workaround is no longer necessary now that the new version of @types/koa has been published. Thanks to @peterblazejewicz, @harryparkdotio, and @orta for the quick upstream fix. Solution: Run `npm update` and remove the `@ts-ignore` comment.
2020-03-27 16:13:31 +00:00
"@types/koa": "^2.11.3",
Add TypeScript definitions for better guardrails Problem: We have TypeScript enabled on the project but have been missing lots of definition files, so there are like 500 errors when you enable `--noImplicitAny`. Solution: Add definitions and fix the bugs that they point out. This reduces the number of errors with `--noImplicitAny` to 285.
2020-03-24 16:21:59 +00:00
"@types/koa-mount": "^4.0.0",
"@types/koa-static": "^4.0.1",
"@types/koa__router": "^8.0.2",
Upgrade Flotilla and SSB-CONN, remove auto-stage Problem: The auto-stage code was a horrible hack that may be causeing an OOM bug if too many peers are staged too quickly. Solution: Since SSB-CONN now supports a variable number of connection hops, we can remove the auto-stage hack and use the default scheduler instead of trying to staple on our own hacky scheduler fix.
2020-05-04 20:18:25 +00:00
"@types/lodash": "^4.14.150",
Bump @types/markdown-it from 0.0.9 to 10.0.3 Bumps [@types/markdown-it](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/markdown-it) from 0.0.9 to 10.0.3. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/markdown-it) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:57:59 +00:00
"@types/markdown-it": "^10.0.3",
Add TypeScript definitions for better guardrails Problem: We have TypeScript enabled on the project but have been missing lots of definition files, so there are like 500 errors when you enable `--noImplicitAny`. Solution: Add definitions and fix the bugs that they point out. This reduces the number of errors with `--noImplicitAny` to 285.
2020-03-24 16:21:59 +00:00
"@types/mkdirp": "^1.0.0",
"@types/nodemon": "^1.19.0",
"@types/pull-stream": "^3.6.0",
Bump @types/sharp from 0.24.0 to 0.26.1 Bumps [@types/sharp](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/sharp) from 0.24.0 to 0.26.1. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/sharp) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:57:17 +00:00
"@types/sharp": "^0.26.1",
Upgrade Flotilla and SSB-CONN, remove auto-stage Problem: The auto-stage code was a horrible hack that may be causeing an OOM bug if too many peers are staged too quickly. Solution: Since SSB-CONN now supports a variable number of connection hops, we can remove the auto-stage hack and use the default scheduler instead of trying to staple on our own hacky scheduler fix.
2020-05-04 20:18:25 +00:00
"@types/supertest": "^2.0.9",
Add TypeScript definitions for better guardrails Problem: We have TypeScript enabled on the project but have been missing lots of definition files, so there are like 500 errors when you enable `--noImplicitAny`. Solution: Add definitions and fix the bugs that they point out. This reduces the number of errors with `--noImplicitAny` to 285.
2020-03-24 16:21:59 +00:00
"@types/yargs": "^15.0.4",
Bump changelog-version from 1.0.1 to 2.0.0 Bumps [changelog-version](https://github.com/AlbertoFdzM/changelog-version) from 1.0.1 to 2.0.0. - [Release notes](https://github.com/AlbertoFdzM/changelog-version/releases) - [Changelog](https://github.com/AlbertoFdzM/changelog-version/blob/develop/CHANGELOG.md) - [Commits](https://github.com/AlbertoFdzM/changelog-version/compare/v1.0.1...v2.0.0) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:19:47 +00:00
"changelog-version": "^2.0.0",
Resolve Travis CI + Windows EOL bug Problem: Travis CI is converting our EOL characters and it's causing problems when we're parsing with Prettier. Solution: Disable auto-conversion.
2020-03-24 02:19:09 +00:00
"common-good": "^2.0.3",
Merge https://github.com/fraction/oasis into advisory-fix-1
2020-04-10 17:51:29 +00:00
"mkdirp": "^1.0.4",
"nodemon": "^2.0.3",
Add very basic test suite Problem: ESLint and TypeScript help catch some types of regressions, but they don't protect us against obvious stuff like "the server won't start". This means that humans need to test a bunch of stuff manually, and that can be really tedious and exhausting. Solution: Yesterday someone invented this cool concept called "testing" where you write automated tests for your software to ensure it actually works the way you expect. It might have beeen invented before yesterday, I don't know. Anyway, this solution adds a bunch of tests that send HTTP GET requests to a bunch of endpoints to make sure the server is at least returning HTTP 200 responses. It also fixes a race condition where HTTP server was available before the readme / version strings were loaded.
2020-04-03 16:07:39 +00:00
"stylelint-config-recommended": "^3.0.0",
Bump supertest from 4.0.2 to 6.0.1 Bumps [supertest](https://github.com/visionmedia/supertest) from 4.0.2 to 6.0.1. - [Release notes](https://github.com/visionmedia/supertest/releases) - [Commits](https://github.com/visionmedia/supertest/compare/v4.0.2...v6.0.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:01:21 +00:00
"supertest": "^6.0.1",
Add very basic test suite Problem: ESLint and TypeScript help catch some types of regressions, but they don't protect us against obvious stuff like "the server won't start". This means that humans need to test a bunch of stuff manually, and that can be really tedious and exhausting. Solution: Yesterday someone invented this cool concept called "testing" where you write automated tests for your software to ensure it actually works the way you expect. It might have beeen invented before yesterday, I don't know. Anyway, this solution adds a bunch of tests that send HTTP GET requests to a bunch of endpoints to make sure the server is at least returning HTTP 200 responses. It also fixes a race condition where HTTP server was available before the readme / version strings were loaded.
2020-04-03 16:07:39 +00:00
"tap": "^14.10.7"
Change rendering engine to use ejs instead of swig
2019-06-24 22:00:10 +00:00
},
Change to make Sharp an optional dependency
2019-12-28 00:28:36 +00:00
"optionalDependencies": {
Bump sharp from 0.25.2 to 0.26.3 Bumps [sharp](https://github.com/lovell/sharp) from 0.25.2 to 0.26.3. - [Release notes](https://github.com/lovell/sharp/releases) - [Changelog](https://github.com/lovell/sharp/blob/master/docs/changelog.md) - [Commits](https://github.com/lovell/sharp/compare/v0.25.2...v0.26.3) Signed-off-by: dependabot[bot] <support@github.com>
2020-11-22 00:32:20 +00:00
"sharp": "^0.26.3"
Make Travis faster by removing double-build Problem: Travis builds PRs and branches, which means that local branches get built twice (!). Solution: Travis should only build `master`, and maybe tags.
2020-01-23 20:09:54 +00:00
},
"bugs": {
"url": "https://github.com/fraction/oasis/issues"
},
"homepage": "https://github.com/fraction/oasis#readme",
"directories": {
Add very basic test suite Problem: ESLint and TypeScript help catch some types of regressions, but they don't protect us against obvious stuff like "the server won't start". This means that humans need to test a bunch of stuff manually, and that can be really tedious and exhausting. Solution: Yesterday someone invented this cool concept called "testing" where you write automated tests for your software to ensure it actually works the way you expect. It might have beeen invented before yesterday, I don't know. Anyway, this solution adds a bunch of tests that send HTTP GET requests to a bunch of endpoints to make sure the server is at least returning HTTP 200 responses. It also fixes a race condition where HTTP server was available before the readme / version strings were loaded.
2020-04-03 16:07:39 +00:00
"doc": "docs",
"test": "test"
Make Travis faster by removing double-build Problem: Travis builds PRs and branches, which means that local branches get built twice (!). Solution: Travis should only build `master`, and maybe tags.
2020-01-23 20:09:54 +00:00
},
Specify exact Node.js engine support and test it Problem: Targeting only the latest version of Node.js and the latest LTS means that we have a sort of rolling backward-compatibility that's hard to reason about. If we break compatibility, we should release those changes as a major version, but the current strategy makes it difficult to tell exactly when we're breaking compatibility. Solution: Specify the exact Node.js versions that we want to support in `package.json` and add the specific tests to `.travis.yml`. In the future we can break compatibility if it's helpful but we'll have to do so explicitly and release the change as a major version.
2020-01-31 18:51:18 +00:00
"keywords": [],
"engines": {
"node": "^10.0.0 || >=12.0.0"
}
.
2019-06-21 16:18:19 +00:00
}
Reference in New Issue Copy Permalink