Nuxt module that allows you to set up a Nuxt 3 project with Shopware Frontends. It provides the composables and api-client packages.
If you want to use these packages with a different Vue.js framework, see the guide for using Shopware Frontends in a custom project.
Install npm package:
# Using pnpm
pnpm add -D @shopware/nuxt-module
# Using yarn
yarn add --dev @shopware/nuxt-module
# Using npm
npm i @shopware/nuxt-module --save-dev
Then, register the module by editing nuxt.config.js or (.ts) file (by extending modules array):
/* nuxt.config.ts */
export default defineNuxtConfig({
/* ... */
modules: [, /* ... */ "@shopware/nuxt-module"],
// set the module config
shopware: {
// connect to your Shopware 6 API instance
endpoint: "https://demo-frontends.shopware.store",
accessToken: "SWSCBHFSNTVMAWNZDNFKSHLAYW",
},
// or directly in the runtime config
// this config will override the base one
runtimeConfig: {
public: {
shopware: {
endpoint: "https://demo-frontends.shopware.store",
accessToken: "SWSCBHFSNTVMAWNZDNFKSHLAYW",
},
},
},
});
Set up your own API instance under shopware key or by extending public runtimeConfiguration in the same file. The nuxt module (and vue plugin) will use those values (runtimeConfig will always override the base ones).
Now you can use any composable function you need without extra import:
<script setup>
const { login } = useUser();
const { refreshSessionContext } = useSessionContext();
refreshSessionContext();
</script>
The information about the session is kept in a cookie (sw-context-token) and used in every request made by any composable or directly, invoked by api instance:
<script>
const { apiClient } = useShopwareContext();
const apiResponse = await apiClient.invoke(/** params omitted */);
</script>
All composable functions are fully typed with TypeScript and they are registed globally in Nuxt.js application, so the type hinting will help you to work with all of them.
Internally, the module uses API Client and Composables packages, configured together to make everything working well. If you need to check how it's working on a different version of one of them, install a package locally in your project (to be installed and available in project's package.json file), then the Nuxt module will use yours. Keep in mind that the different configuration may lead to unexpected behavior.
You can use Nuxt config to set the default API call headers. More about Nuxt configuration can be found HERE.
NOTE: By default, the values in
runtimeConfigare only available on the server-side. However, keys withinruntimeConfig.publicare also accessible on the client-side. MORE
{
"runtimeConfig": {
"public": {
"apiClientConfig": {
"headers": {
"global-heder-example": "global-header-example-value"
}
}
},
"apiClientConfig": {
"headers": {
"ssr-heder-example": "ssr-header-example-value"
}
}
}
}
#composable-frontends)Full changelog for stable version is available here