You're Invited: Meet the Socket team at BSidesSF and RSAC - April 27 - May 1.RSVP
Socket
Sign inDemoInstall
Socket

aem-front

Package Overview
Dependencies
Maintainers
1
Versions
20
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

aem-front

AEM Front speeds up development in AEM significantly. It combines AEMSync with BrowserSync, and also works together with the AEM Front Extension for Google Chrome so you don't have to manually inject the BrowserSync script into your code base.

0.3.0
latest
Source
npm
Version published
Weekly downloads
1.3K
1.11%
Maintainers
1
Weekly downloads
 
Created
Source

AEM Front

AEM Front speeds up development in AEM significantly. It combines AEMSync with BrowserSync, and also works together with the AEM Front Extension for Google Chrome so you don't have to manually inject the BrowserSync script into your code base.

Installation

npm install aem-front -g

Usage

aem-front

You can also specify one or multiple of the following options:

-w: Folder to watch; default is current (`CWD`).
-t: URL to AEM instance; multiple can be set. Default is http://admin:admin@localhost:4502.
-e: Anymatch exclude filter; any file matching the pattern will be skipped. Default is `**/jcr_root/*, **/@(.git|.svn|.hg|target), **/@(.git|.svn|.hg|target)/**`
-o: Browser page to be opened after successful launch; default is "false".
-b: Browser where page should be opened in; this parameter is platform dependent; for example, Chrome is "google chrome" on OS X, "google-chrome" on Linux and "chrome" on Windows; default is "google chrome".
-i: Update interval in milliseconds; default is 100.
-v: Display version of AEM Front.

Examples:

aem-front -w "./../sibling/my_project" -e "**/webpack.module/**" -i "500"

aem-front -t http://admin:admin@localhost:4502 -t http://admin:admin@localhost:4503 -w ~/workspace/my_project

Requirements

  • NodeJS and NPM
  • Required if you want to use the corresponding Chrome extension: Chrome Browser

Step-by-step guide

  • If you do not have Node and NPM installed, in command line run:
sudo brew install node
sudo npm install npm -g
  • Install AEM Front by running:
npm install aem-front -g
  • Run the command listed in the "Usage" section in your terminal from a folder where you want to watch file changes. But you can basically run it from anywhere as long as you pass the correct path with the -w option.

  • After successfully starting this script, you can/should install the corresponding Chrome extension. The script injects the required BrowserSync script automatically into your website and comes with a few handy configuration options. But you can also past the BrowserSync script into your website manually. You can install the extension directly from the Chrome app store: https://chrome.google.com/webstore/detail/cmpbphecgagbhhociicpakhddeagjlih

Development

If you clone this project (aem-front) to your local machine and modify it, you can test changes without having to push and publish them to the NPM repository. Do this by linking aem-front globally. In your terminal, run:

npm link

Then, in your project where you want to test the local aem-front instead of the one hosted at npmjs.com, run:

npm link aem-front

Thanks to the BrowserSync team and to gavoja for aemsync.

Keywords

AEM

FAQs

Package last updated on 13 Jun 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts