# Wildcard don't work in config.json

**URL:** https://discourse.roots.io/t/wildcard-dont-work-in-config-json/13865
**Category:** sage
**Tags:** gulp, webpack, sage9
**Created:** 2018-10-15T22:24:09Z
**Posts:** 3

## Post 1 by @iliakarasin — 2018-10-15T22:24:09Z

```
{
  "entry": {
    "main": [
      "./scripts/main.js",
      "./scripts/components/*.js", //this example currently does not compile & errors out
      "./styles/main.scss"
    ]
  },
}
```

In Gulp/Bower – manifest.json allows you to pass wildcards (aka folders of JS / SCSS files) to include for compilation; this is not currently possible in Sage 9.

In order to utilize config.json each individual file must be listed; this is inefficient and nonpragmatic.

---

## Post 2 by @alwaysblank — 2018-10-15T22:49:52Z

It looks like this is a limitation of Webpack: [https://github.com/webpack/webpack/issues/370](https://github.com/webpack/webpack/issues/370) That thread also offers some relatively simple ways to address the issue. AFAIK the usual development method w/ Sage is to `import` or `require` additional scripts in `main.js` rather than importing them through `config.json`.

---

## Post 3 by @iliakarasin — 2018-10-15T23:01:05Z

Ah wonderful, thanks for pointing me in the right direction.