Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Running 'gulp build', but no output directory is created.

See original GitHub issue

Hi,

I am running ‘gulp build’ inside the semantic folder, but no output directory is created.

$ gulp build
[15:38:09] Using gulpfile ~/XX/XX/semantic/gulpfile.js
[15:38:09] Starting 'build'...
Building Semantic
[15:38:09] Starting 'build-javascript'...
Building Javascript
[15:38:09] Starting 'build-css'...
Building CSS
[15:38:09] Starting 'build-assets'...
Building assets
[15:38:09] Starting 'package compressed js'...
[15:38:09] Starting 'package uncompressed js'...
[15:38:09] Finished 'build-javascript' after 78 ms
[15:38:09] Starting 'package uncompressed css'...
[15:38:09] Starting 'package compressed css'...
[15:38:09] Finished 'build-assets' after 51 ms
[15:38:09] Finished 'package uncompressed js' after 24 ms
[15:38:09] Finished 'package uncompressed css' after 17 ms
[15:38:09] Finished 'package compressed js' after 34 ms
[15:38:09] Finished 'package compressed css' after 10 ms
[15:38:09] Finished 'build-css' after 72 ms
[15:38:09] Finished 'build' after 99 ms

Build Javascript and Build CSS appear in blue text.

Versions:

Semantic --> 2.2.6 NPM --> 3.10.8 Gulp --> 3.9.1 Node --> v6.9.1

Issue Analytics

State:
Created 7 years ago
Comments:8 (3 by maintainers)

Top GitHub Comments

86reactions

vixandradecommented, Nov 30, 2016

Hi, I’ve been struggling with this issue for a while, but I’ve finally come up with a solution.

By digging through the task scripts on /semantic/tasks I’ve discovered that the gulp tasks expected the semantic.json file to be on the root of the semantic folder and not on root of the project directory - where it was created by default in my case.

I just moved the semantic.json from the project root to the semantic folder and ran ‘gulp build’ again. Now I have the /dist folder as expected!

I’ve found some other threads with this same issue, so I believe it would be worth a look at the Semantic UI installation script. Other issues are: #4565 #4481 #4326 , and I’m tagging @jlukic because he was the one to close some of those due to lack of information.

3reactions

LorenzoFernandocommented, Feb 14, 2017

The solution given by vixandrade works for me as well. I will look into this myself, but is there a way to ensure that semantic.json is placed in the correct directory moving forward?