rename kinto.js to a better name

[glasserc]

A better name for kinto.js should reference the fact that it is offline-first, based on IndexedDB, and/or provides the notion of adapters.

kinto-offline seems misleading and kinto-offline-first seems too long.

Any other ideas?

[n1k0]

@DirtyF suggested kinto-sync.js which sounds rather nice.

[Natim]

What about kinto-local-sync.js

[n1k0]

kinto-browser.js? I like it kinda contains O'Brother

[almet]

kinto-browser-sync ? (because kinto-http could also be used from inside a browser)

[Natim]

Other great propositions from the meeting:

• kinto-storage.js
• kinto-offline.js
• kinto-offlinefirst.js

[glasserc]

kinto-disconnected.js?

[glasserc]

Ooh! How about "kinto-unplugged.js"?

[n1k0]

Ooh! How about "kinto-unplugged.js"?

Now I really like this one :)

[almet]

I love it as well :)

[leplatrem]

https://twitter.com/pouchdb/status/754016070546051072?s=09

[leplatrem]

@chartjes instinctively suggested kinto-sync.js, so I guess that it will be!

• kinto-sync for the npm package
• kinto-sync.js for the Github package

[dstaley]

@leplatrem sorry to revive an almost four-year-old conversation, but do you still want to do this? If so, I have some thoughts, but if not please feel free to close this issue :)

[leplatrem]

Yes! Feel free to tackle this!

[dstaley]

kinto.js currently does two things:

1. Store, query, and retrieve arbitrary data
2. Sync that data with a remote server

While the first is the core feature of the library, the second is actually completely optional. You can use kinto.js without the sync feature, and thus without kinto-http.js. With that in mind, I propose that we name the library either kinto-db or kinto-storage. I'm kind of partial to kinto-db, since it allows us to grow the storage/querying features of the library without feeling boxed in by the name. I think either db or storage implies that the client is actually storing data, rather than simply retrieving it from a server. When we add new adapters, they can be named kinto-adapter-engine (so, for example, kinto-storage-sqlite).

It could look something like this:

import { DB } from "kinto-db";

const db = new DB();
const collection = db.collection("articles");

import { Storage } from "kinto-storage";
import { SqliteAdapter } from "kinto-adapter-sqlite";

const storage = new Storage({
  adapter: (name, options) => new SqliteAdapter(name, options),
});
const collection = storage.collection("articles");

I'm also considering moving all our JavaScript packages to an npm org, so the package names would look like:

• @kinto/storage
• @kinto/http
• @kinto/adapter-sqlite

[leplatrem]

I like kinto-db, as well as kinto-offline or kinto-storage :)

But I'm not sure about adapter in package names. This is more like a programming pattern notion than anything else. Suffixing the main name should be enough IMO (eg. kinto-db-sqlite, kinto-storage-websql, ...)

I'm also considering moving all our JavaScript packages to an npm org, so the package names would look like:

Good idea! Let's do that!