Sage 8.6.0 - Gulp Error

qpiddigital · July 20, 2020, 10:50pm

Hello,

I’m getting an error when running Gulp and compiling my assets using Sage 8.6.0:

let isMatch = picomatch(String(patterns[i]), { …options, onResult }, true);
SyntaxError: Unexpected token …

Anybody come across this error before?

My Gulp build process has been working fine up until now

Many thanks,
Ollie

strarsis · July 20, 2020, 10:53pm

Maybe an incompatibility with a older/newer node version?
Ensure a node version that is known to build correctly is used, by using a node version manager like [nvm](https://github.com/nvm-sh/nvm).
Requirements for Sage 8.6 (last 8. release):

github.com

roots/sage/blob/8.6.0/README.md#requirements

# [Sage](https://roots.io/sage/)
[![Build Status](https://travis-ci.org/roots/sage.svg)](https://travis-ci.org/roots/sage)
[![devDependency Status](https://david-dm.org/roots/sage/dev-status.svg)](https://david-dm.org/roots/sage#info=devDependencies)

Sage is a WordPress starter theme based on HTML5 Boilerplate, gulp, Bower, and Bootstrap Sass, that will help you make better themes.

* Source: [https://github.com/roots/sage](https://github.com/roots/sage)
* Homepage: [https://roots.io/sage/](https://roots.io/sage/)
* Documentation: [https://roots.io/sage/docs/](https://roots.io/sage/docs/)
* Twitter: [@rootswp](https://twitter.com/rootswp)
* Newsletter: [Subscribe](http://roots.io/subscribe/)
* Forum: [https://discourse.roots.io/](https://discourse.roots.io/)

## Requirements

| Prerequisite       | How to check | How to install
| ------------------ | ------------ | ------------- |
| PHP >= 5.4.x       | `php -v`     | [php.net](http://php.net/manual/en/install.php) |
| Node.js >= 6.9     | `node -v`    | [nodejs.org](http://nodejs.org/) |
| gulp-cli >= 2.0.0  | `gulp -v`    | `npm install -g gulp-cli` |

This file has been truncated. show original

Node.js >= 6.9, so try building the theme starting with node version 6.9:

$ nvm install 6.9
$ nvm use 6.9

$ gulp
# or
$ gulp --production

When you found a working node version, you may want to add a .nvmrc file to the project with that version to document it and automatically lock that version in when entering the directory, it also helps when deploying with Trellis as it the deploy script can be easily modified to invoke node/npm with nvm and ensure the proper node version is used during the build.

qpiddigital · July 20, 2020, 10:58pm

I’m using and have been using node 6.9.5 for sometime now.

It’s been working fine up until now

strarsis · July 20, 2020, 10:58pm

Are you sure that you are indeed using node v6.9 for building?
node -v in the theme directory…

Remove the whole node_modules and npm install again.
Be wary of npm audit because it could update packages in a breaking way.
Also ensure the package lock file is checked out and is known to build.

Related issues concerning the node version used (maybe try a newer node version?):

carlosfaria · July 22, 2020, 9:12am

Didn’t see this thread, sorry: