Gecko [ admjudic.com.br ]

Name	Size	Permission
README.md	242 B	-rw-r--r--
block.md	398 B	-rw-r--r--
development.md	1.49 KB	-rw-r--r--
install.md	255 B	-rw-r--r--

Code Editor : development.md

# Development

This guide details how to work with the NPM build process to compile the SCSS.

## NPM Process

- SCSS to CSS compiling
- Autoprefixing

## Setup Local Dev Environment

1. You will need Node.js/NPM installed on your computer. You can check if you already have Node.js installed by running `node -v`, if you see a version number, it’s installed. If not, follow installation instructions for your OS here: [https://nodejs.org/](https://nodejs.org/).
2. Navigate to the plugin root directory in the command line and install the plugin dependencies: `npm ci`. You may need to run `sudo npm ci` depending on OS permissions. We use `npm ci` instead of `npm install` here to preserve a consistent dev environment by forcing the install to read from the package-lock.json file. This will produce a faster and more reliable dev environment across teams/products. Read more here about why ci here: [https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable.html](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable.html)

## Working with SCSS

You should now be able to run the build task from inside the plugin's root directory. When the SCSS is compiled, NPM will create a *styles.css* file in the plugin root directory and add any necessary vendor prefixes. This file should then be automatically loaded by the plugin. Do not edit this file directly. All style changes must be done in the SCSS directory.

- To compile the SCSS for production: `npm run build`

${this.title}

Code Editor : development.md