This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@verdant-web/server@3.0.0
Major Changes
43edd7a: Migration of server code required
Introduces support for custom server storage solutions via interface implementation. This change also makes server storage queries and writes async (they weren't before), which improves compatibility with custom solutions and performance overall with high message concurrency.
Server migration
Previously, you'd create a new Verdant server like so:
new VerdantServer({
databaseFile: './path/to/db.sqlite',
});
Now, you should import sqlStorage from @verdant-web/server/storage and provide it to the storage parameter:
new VerdantServer({
storage: sqlStorage({
databaseFile: './path/to/db.sqlite',
}),
});
That's all that's needed. Remember to also upgrade your client to handle some small tweaks to sync protocols. They should be non-breaking, but it's better to be safe here.
Patch Changes
Updated dependencies [43edd7a]
@verdant-web/common@2.3.0
@verdant-web/common@2.3.0
Minor Changes
43edd7a: Migration of server code required
Introduces support for custom server storage solutions via interface implementation. This change also makes server storage queries and writes async (they weren't before), which improves compatibility with custom solutions and performance overall with high message concurrency.
Server migration
Previously, you'd create a new Verdant server like so:
new VerdantServer({
databaseFile: './path/to/db.sqlite',
});
Now, you should import sqlStorage from @verdant-web/server/storage and provide it to the storage parameter:
new VerdantServer({
storage: sqlStorage({
databaseFile: './path/to/db.sqlite',
}),
});
That's all that's needed. Remember to also upgrade your client to handle some small tweaks to sync protocols. They should be non-breaking, but it's better to be safe here.
@verdant-web/store@3.4.0
Minor Changes
43edd7a: Migration of server code required
Introduces support for custom server storage solutions via interface implementation. This change also makes server storage queries and writes async (they weren't before), which improves compatibility with custom solutions and performance overall with high message concurrency.
Server migration
Previously, you'd create a new Verdant server like so:
new VerdantServer({
databaseFile: './path/to/db.sqlite',
});
Now, you should import sqlStorage from @verdant-web/server/storage and provide it to the storage parameter:
new VerdantServer({
storage: sqlStorage({
databaseFile: './path/to/db.sqlite',
}),
});
That's all that's needed. Remember to also upgrade your client to handle some small tweaks to sync protocols. They should be non-breaking, but it's better to be safe here.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@verdant-web/server@3.0.0
Major Changes
43edd7a: Migration of server code required
Introduces support for custom server storage solutions via interface implementation. This change also makes server storage queries and writes async (they weren't before), which improves compatibility with custom solutions and performance overall with high message concurrency.
Server migration
Previously, you'd create a new Verdant server like so:
Now, you should import
sqlStorage
from@verdant-web/server/storage
and provide it to thestorage
parameter:That's all that's needed. Remember to also upgrade your client to handle some small tweaks to sync protocols. They should be non-breaking, but it's better to be safe here.
Patch Changes
@verdant-web/common@2.3.0
Minor Changes
43edd7a: Migration of server code required
Introduces support for custom server storage solutions via interface implementation. This change also makes server storage queries and writes async (they weren't before), which improves compatibility with custom solutions and performance overall with high message concurrency.
Server migration
Previously, you'd create a new Verdant server like so:
Now, you should import
sqlStorage
from@verdant-web/server/storage
and provide it to thestorage
parameter:That's all that's needed. Remember to also upgrade your client to handle some small tweaks to sync protocols. They should be non-breaking, but it's better to be safe here.
@verdant-web/store@3.4.0
Minor Changes
43edd7a: Migration of server code required
Introduces support for custom server storage solutions via interface implementation. This change also makes server storage queries and writes async (they weren't before), which improves compatibility with custom solutions and performance overall with high message concurrency.
Server migration
Previously, you'd create a new Verdant server like so:
Now, you should import
sqlStorage
from@verdant-web/server/storage
and provide it to thestorage
parameter:That's all that's needed. Remember to also upgrade your client to handle some small tweaks to sync protocols. They should be non-breaking, but it's better to be safe here.
Patch Changes
@verdant-web/s3-file-storage@1.0.16
Patch Changes
@verdant-web/react@29.0.0
Patch Changes