Releases: junobuild/plugins
Releases · junobuild/plugins
v0.0.16
v0.0.15
@junobuild/nextjs|vite-plugin
Build
- Bump cli-tools and config dependency.
v0.0.14
@junobuild/nextjs|vite-plugin
Documentation
- Provides the plugins with some JSDocs.
v0.0.13
@junobuild/nextjs|vite-plugin
Build
- Bump junobuild dependencies for config.
- Clean up dependencies to reference only
@junobuild/plugin-tools
.
v0.0.12
@junobuild/nextjs|vite-plugin
Fix
- Throw an error if Juno config is not resolved only if the container should not be used - i.e. assert the file exists only for other context than local development.
v0.0.11
@junobuild/nextjs|vite-plugin
Features
- Throw an error if Juno config is not resolved only for mode
production
else console warn.
v0.0.10
@junobuild/nextjs-plugin
Features
- Make the next config optional and set per default the output to
export
.
v0.0.9
This release introduces a new plugin @junobuild/nextjs-plugin for configuring Juno in Next.js applications. 🚀
Since this plugin shares code similarities with the vite plugin, it also includes a new library @junobuild/plugin-tools to prevent code duplication.
v0.0.8
Breaking Changes ⚠️
- The
satelliteId
andorbiterId
configurations are marked as deprecated, and thesatellitesIds
property has been removed. Instead, useid
andids
for configuringsatellites
andorbiters
injuno.config.ts|js|json
.
v0.0.7
@junobuild/vite-plugin
Breaking Changes
- The
container
parameter remains optional and continues to accept aboolean
. However, it now also accepts anobject
instead of astring
. - The plugin will now bubble up errors instead of catching them. This change ensures that if expectations are not met, the build process will halt.
Features
- Added support for the configuration file
juno.config.ts|js|json
. - Implemented injection of environment variables for ICP ledger and index canisters.
Unreleased
Features
- Initialization of the work to provide in the future React hooks.