Skip to content

aemsites/vg-macktrucks-com

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2,985 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Mack Trucks

EDS sites for macktrucks.com

Environments

Other markets:

bahamas.macktrucks.com

macktrucks.ca

macktrucks.cl

macktrucks.co.nz

macktrucks.com.ar

macktrucks.com.au

macktrucks.com.bo

macktrucks.com.co

macktrucks.com.do

macktrucks.com.ec

macktrucksemea.com

macktrucksguyana.com

macktrucks.com.mx

macktrucksnigeria.com

macktrucksnicaragua.com

macktrucks.com.pa

macktrucks.com.pe

macktrucks.com.ve

macktrucks.cr

macktrucks.gt

macktrucks.hn

macktrucks.ht

sv.macktrucks.com

tt.macktrucks.com

Local Development

  1. Install the Helix CLI: npm install -g @adobe/aem-cli and install dev dependencies:
npm ci
  1. Start the local development environment with a single command:
npm start

This runs the AEM proxy aem up and the build npm run watch in parallel (via npm-run-all), so you get automatic rebuilds and the AEM proxy in one step.

  1. If you prefer the old workflow, you can still run the commands separately:
  • aem up — start the AEM proxy
  • npm run watch — start the incremental build with sourcemaps
  1. Open the {repo} directory in your favorite IDE and start coding :)

Volvo Design System Setup

  1. Configure your local environment to be able to install the Volvo Design System packages. Follow the guide here.
  2. Configure your PAT token and email in your user-level .npmrc (e.g., ~/.npmrc), not in the project directory, to avoid authentication issues. Refer to the official documentation for details (2.1 Authentication).

To follow the “Copy the token and base64 encode the string” step from the instructions, you can generate the base64-encoded PAT like this:

echo -n YOUR_PAT_HERE | base64

Use the resulting string as the value for the _password field in your .npmrc.

Debugging Production Code Using Local Sourcemaps

Production builds do not include sourcemaps.

To debug a production issue:

  1. Check out the exact commit currently deployed to production (usually the latest commit on main, or a specific commit SHA if needed).
  2. Build locally (sourcemaps enabled):
npm run build:dev
  1. Open the production page in your browser and access its developer tools, then navigate to the panel where source files are displayed (e.g. Sources).
  2. Add your local dist/ folder to the workspace / file system mapping (name varies by browser).

You can then use your local sourcemaps to inspect and debug the original source code behind the minified production files. Depending on the browser, the mapping may happen automatically or may require a manual file-to-file association within the developer tools.

About

EDS site for https://www.macktrucks.com

Resources

Stars

Watchers

Forks

Packages

 
 
 

Contributors