0.1.1 • Published 3 years ago

@recart/nacelle-nuxt-module v0.1.1

Weekly downloads
496
License
MIT
Repository
github
Last release
3 years ago

Recart integration for Nacelle

Recart works out of the box on normal Shopify storefronts.

However, if you have a Nacelle site, you need to install this Nuxt module to make Recart work.

Requirements

Usage

  1. Install our package.

    npm install @recart/nacelle-nuxt-module
  2. Add the module to your Nacelle app.

    Open nuxt.config.js and add @recart/nacelle-nuxt-module to the modules array, along with your Recart Site ID.

    It should look like this:

    modules: [
      '@nuxtjs/pwa',
      '@nuxtjs/dotenv',
      '@nacelle/nacelle-nuxt-module',
      '@nuxtjs/sitemap',
      ['@recart/nacelle-nuxt-module', { recartSiteId: '5abcdefgh000000000000000' }]
    ],

    You can find your Site ID on the Recart dashboard: app.recart.com/settings/me

  3. Add our metafields to the checkout object.

    Open store/checkout.js and find the this.$nacelle.checkout.process method call. In a fresh Nacelle install, it looks like this:

    let checkout = await this.$nacelle.checkout.process({ cartItems, checkoutId })

    To help Recart identify checkouts and orders, extend this line with metafields, like this:

    let checkout = await this.$nacelle.checkout.process({
      cartItems,
      checkoutId,
      metafields: this.$recart.getMetafieldsForCheckout() // <-- add this line
    })

Support

If you have any questions, feel free to contact Recart support at support@recart.com.

Contributing

We really appreciate contributions.

If you have identified a bug, please open an Issue and provide as with as many details as possible.

If you have a suggestion to make the code better, feel free to submit a Pull Request. We only ask a few things from you:

  • Write a short PR description, explaining the purpose of your solution.
  • Write descriptive commit messages.
  • Format the code according to the Standard JS guidelines and make sure the npm run lint command runs without errors.
  • If possible, cover your changes with tests and make sure the npm test command runs without errors.
0.1.0

3 years ago

0.1.1

3 years ago

0.0.10

3 years ago

0.0.9

3 years ago

0.0.8

3 years ago

0.0.7

3 years ago

0.0.6

3 years ago

0.0.4

3 years ago

0.0.3

3 years ago

0.0.2

3 years ago

0.0.1

3 years ago