Building the Spartacus Storefront from Libraries

The following instructions describe how to build a storefront application using published Spartacus 1.x libraries.

If you are building Spartacus from source, see Contributor Setup.

Prerequisites

Before carrying out the procedures below, ensure the following front end and back end requirements are in place.

Front-End Development Requirements

Your Angular development environment should include the following:

  • Angular CLI: 8.2.5 or later, < 9.0.0
  • node.js: 10.14.1 or later, < 12
  • yarn: 1.15 or later

Installing or Updating the Prerequisite Development Tools

There are a few ways you can install Angular and other prerequisite software. The following example installs yarn, node.js, and Angular CLI using Homebrew, which was created for MacOS but also works on Linux and Windows 10 (through the Linux subsystem feature).

To install the prerequisite development tools, install Homebrew, and then run the following commands:

brew install yarn
brew install node@10
brew install angular-cli

To update existing installations, use brew upgrade instead of brew install.

Note:

  • If you have a later version of node.js installed in addition v10, you can set v10 to be used with the following command: brew link --force --overwrite node@10
  • Installing Homebrew and the prerequisites is beyond the scope of this document. You can also install the prerequisites using their individual installers.

Back End Server Requirements

Spartacus uses SAP Commerce Cloud for its back end, and makes use of the sample data from the B2C Accelerator Electronics storefront in particular.

Release 1905 (latest patch) is recommended.

For more information, see Installing SAP Commerce Cloud for use with Spartacus. If you are not using the latest version of SAP Commerce Cloud, see Working with Older Versions of SAP Commerce Cloud for installation instructions appropriate to your version.

Creating a New Angular App

The following procedure describes how to create a new Angular application with the name mystore.

  1. Open a terminal or command prompt window at the location of your choice.

  2. Using the Angular CLI, generate a new Angular application with the following command:

    ng new mystore --style=scss

    When prompted if you would like to add Angular routing, enter n for ‘no’.

    The mystore folder and the new app are created.

  3. Access the newly created mystore folder with the following command:

     cd mystore

Project Setup

The easiest way to start a new project is to use Angular Schematics to quickly set up your application.

Spartacus support command which allows for full application scaffold with features like PWA or SSR:

    ng add @spartacus/schematics --pwa --ssr

Note: --pwa and --ssr are optional and can be used separately.

This command includes configuration parameters, such as baseUrl or baseSite. Usage example:

    ng add @spartacus/schematics --baseUrl https://my.occ.server.url --baseSite my-site

After the project is set up using schematics:

  1. Inspect the src\app\app.module.ts file for any changes you want to make for your setup. For example, you might want to change the baseUrl to point to your server and the basesite to corresond with the WCMS site. You likely also want to specify the compatibility version by changing features.level, as the default might not be the latest version.

  2. Replace the contents of mystore/src/app/app.component.html with <cx-storefront>Loading...</cx-storefront>

  3. Run yarn start.

For a full list of available parameters please visit Spartacus schematics documentation.

Setting up a Storefront Manually

Although we recommend using Schematics, there might be situations when you want to build your application from scratch.

The dependencies in this procedure are required by the Spartacus storefront.

  1. Open mystore/package.json using a text editor.

  2. Add the following dependencies to the end of the dependencies section of package.json.

    "@angular/pwa": "^0.803.2",
"@angular/service-worker": "~8.2.5",
"@ng-bootstrap/ng-bootstrap": "5.1.0",
"@ng-select/ng-select": "^3.0.7",
"@ngrx/effects": "~8.3.0",
"@ngrx/router-store": "~8.3.0",
"@ngrx/store": "~8.3.0",
"ngx-infinite-scroll": "^8.0.0",
"bootstrap": "^4.2.1",
"i18next": "^15.0.6",
"i18next-xhr-backend": "^2.0.1",

 "@spartacus/core": "~1.3.0",
 "@spartacus/styles": "~1.3.0",
 "@spartacus/storefront": "~1.3.0",
 "@spartacus/assets": "~1.3.0"

    Note: Make sure to add a comma to the end of the last dependency statement listed in this section. For example, the last statement in your new app might be "zone.js": "~0.9.1" so you would need to add a comma after 0.9.1".

  3. From the terminal window, within mystore, install the dependencies by running the following command:

    yarn install

Note:

(1) Using ~ instructs yarn to use the latest patch version (x.y.z), whereas using ^ instructs yarn to use the latest minor version (x.y.0).

(2) If you are updating an existing app, and changing dependencies, it’s recommended that you delete the node_modules folder before running the install command.

Adding Import Declarations and Storefront Configuration Settings

To use Spartacus, your new Angular app needs to import Spartacus libraries.

  1. Open mystore/src/app/app.module.ts using a text editor.

  2. Add the following lines to the top of the file, below existing import statements.

     import { translations, translationChunksConfig } from '@spartacus/assets';
 import { B2cStorefrontModule } from '@spartacus/storefront';

  3. Add the following lines to the NgModule/imports section, below the existing BrowserModule statement, but before the last ], (closing square bracket):

     B2cStorefrontModule.withConfig({
   backend: {
     occ: {
       baseUrl: 'https://localhost:9002',
       prefix: '/rest/v2/'
     }
   },
   context: {
     baseSite: ['electronics-spa']
   },
   i18n: {
     resources: translations,
     chunks: translationChunksConfig,
     fallbackLang: 'en'
   },
   features: {
     level: '1.3'
   }
 }),

    Don’t forget to add a comma to the module entry before B2cStorefrontModule.

  4. Save the file.

    The final version of mystore/src/app/app.module.ts should look like this:

    import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
   
import { AppComponent } from './app.component';
import { translations, translationChunksConfig } from '@spartacus/assets';
import { B2cStorefrontModule } from '@spartacus/storefront';
   
@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    B2cStorefrontModule.withConfig({
      backend: {
        occ: {
          baseUrl: 'https://localhost:9002',
          prefix: '/rest/v2/'
        }
      },
      context: {
        baseSite: ['electronics-spa']
      },
      i18n: {
        resources: translations,
        chunks: translationChunksConfig,
        fallbackLang: 'en'
      },
      features: {
        level: '1.3'
      }
    }),
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

Note: Some of the statements in the example above were generated by Angular when you first created the app.

About the Import Statements

The import statements import either modules or default data needed by Spartacus.

About the B2cStorefrontModule Settings

The B2cStorefrontModule settings are described in more detail in the Spartacus documentation. The following is a brief summary in case you want to change them.

  • backend.occ (baseUrl, prefix, legacy): When combined, the baseUrl, prefix, and legacy parameters form the basis for all OCC REST API calls to your SAP Commerce Cloud server. The value of https://localhost:9002 is valid if you have installed SAP Commerce Cloud on a local machine. The value of rest/v2 is the default OCC REST API path. The value of false is the default for anyone using 19.05 and above, however you can change it to true if you are using 18.11 and below. Change these values depending on the URL of your SAP Commerce Cloud server, and your prefix configuration.

    Note: Your server is properly configured if you can display the Open API documentation (for example, https://localhost:9002/rest/v2/swagger-ui.html)

  • site (baseSite): The value for baseSite is the CMS name of the back end storefront, as it appears in Backoffice > WCMS > Website. This example uses the electronics sample storefront included with SAP Commerce Cloud. Change this value based on the CMS sites installed on your server. For example, if you install the spartacussampledataaddon (described later in this document), you would use electronics-spa base site value.

    Note: The base site and its context can also be detected automatically, based on URL patterns defined in the CMS. For more information, see Context Configuration.

  • i18n (resources, fallbackLang): This parameter configures Spartacus to use default translation data provided with Spartacus and defines the language to use if a translation doesn’t exist.

  • features: Configure feature level available in an app. Value corresponds to minor (feature) release version number: ‘1.0’, ‘1.1’, etc. Each subsequent level contains all of the features from previous one.

Adding the Storefront to app.component.html

This procedure adds the storefront component cx-storefront to app.component.html. Doing so will display your storefront app in your browser.

  1. Open mystore/src/app/app.component.html with a text editor.

  2. Replace the entire contents of the file with the following line:

    <cx-storefront>Loading...</cx-storefront>

Adding Default Styling

This procedure adds the default Spartacus styling to your storefront. Without it, your storefront app will not display properly.

  1. Open mystore/src/styles.scss with a text editor.

  2. Add the following line:

    @import "~@spartacus/styles/index";

Building and Starting

This section describes how to validate your back end installation, and then start the application with the storefront enabled.

Validating the SAP Commerce Cloud Backend

Note: The Chrome browser is recommended and used in the following example, but other browsers can be used as long as they recognize and allow you to continue even though a site is using a self-signed certificate.

  1. Use a web browser to access the OCC endpoint of your backend.

    The default is available at: {server-base-url}/rest/v2/electronics/cms/pages.

    For example, with a back end instance running from https://localhost:9002, you would access: https://localhost:9002/rest/v2/electronics/cms/pages

  2. Accept the security exception in your browser, if you are running a development instance with a self-signed HTTPS certificate.

    When the request works, you see an XML response in your browser.

Starting the Storefront Application

To start your Spartacus storefront, enter the following command from mystore in your terminal window:

yarn start

When the app server is properly started, point your browser to http://localhost:4200.

Or, to start your Spartacus storefront securely, enter the following command:

yarn start --ssl

Then point your browser to https://localhost:4200.

If you are using the electronics sample store that is included with SAP Commerce Cloud, you may notice that the logo is small and difficult to see. This is because the logo was designed for Accelerator templates. The logo comes from the server and can be updated.

  1. Log in to SAP Commerce Backoffice.

  2. Select WCMS in the left-hand navigation pane, then select the Component child node that appears below.

  3. Search for the term SiteLogoComponent in the Search box in the top-center panel.

    You can modify the component directly in the Online Catalog, or you can modify it in the Staged Catalog and then perform a sync.

  4. Open the Administration tab of the SiteLogoComponent, and remove the Media value.

  5. Click the button labelled … next to the Media field.

  6. In the pop-up search box that appears, search for the desired media file in your system and select it.

  7. Save your changes.

Instructions for using Incremental Unreleased Spartacus Libraries

(last updated June 10, 2019)

Spartacus libraries are usually released every two weeks. We test the libraries before releasing.

If you wish, you can use incremental but unreleased Spartacus libraries. These libraries are essentially what’s been merged to our develop branch but not part of an official release.

Note: Incremental libraries are not yet tested. We may not answer questions in the Spartacus help chat about incremental releases. Use at your own risk.

To use the incremental libraries, substitute the following in your package.json file.

"@spartacus/core": "SAP/cloud-commerce-spartacus-storefront-core-builds",
"@spartacus/styles": "SAP/cloud-commerce-spartacus-storefront-styles-builds",
"@spartacus/storefront": "SAP/cloud-commerce-spartacus-storefront-storefront-builds",

The Spartacus Assets library is not yet available as an incremental release.