Problem building all components

Hi,

Untill all the versions of Fomantic UI (except the latest 2.8.6) when I executed the command npx gulp build on my terminal, it would build ALL components inside dist/components directory (minified and not minified) and after that it would build the semantic.min.css and semantic.min.js WITH ONLY the components that I specified at components item inside semantic.json file.

However, in the latest Fomantic UI version, it only builds in the dist/components directory the components specified inside the semantic.json file and nothing else. This behaviour is not desirable since most times I just want to generate the semantic.min.js file with some specific components, but I also want to have all the other components built, ready to be imported in any project only when needed.

Is there a switch/flag I can use to make the behaviour of all previous version work again?

[batata004]

@ko2in I did exactly the same as you did, and I also tried a “random” version 2.7.2 and the behaviour was the same: all minified and non minified versions were created in the /dist directory BUT the semantic.min.js and semantic.min.css files contained only the specified components. PS: I always delete the /dist directory before building, however I realize that the files are automatically deleted even if I dont do that. I came to that conclusion doing this: I made a build and waited the files being created. After that I opened a random file (like checkbox.min.js) and changed the contents. Then I built it again. When I open the checkbox.min.js file, the contents were changed (it means that what I had changed previously was removed and the new content overwrited my content).

I knew that this would happen, cause I build custom Fomantic files for a while using this computer and this always happened. But since you reported doing the same and having different results than me, I went to my wife’s computer and installed everything there. When I built the Fomantic, the behaviour was exactly as YOU described (not me!).

So I was wondering: what did I do in my computer that may have changed some default configuration? I had no idea, cause I am not an advanced user of npm and such. So I removed node from my computer, restarted, installed everything again and boom, it worked exactly as you said @ko2in !!!

So, there should be some configuration that I may have messed up or setted on node that changed it’s behaviour. I usually build lots of other libraries with node and maybe something in some library made some change to my configurations on node.

Anyway, I apoligize for taking so long of your time guys, and I can clearly confirm that I was doing something weird and the new version works exactly as latest in terms of build process!

BTW I loved the granularity that the transition customization brought to this build. Thanks a lot @lubber-de !!!

[ko2in]

@batata004 I’ve tested several times, and found no differences. Here’s what I did with version 2.7.4:

• npm install fomantic-ui@2.7.4
• Install with all default configs and all components, and ran npx gulp build.
• Now, I got all components in /dist/components directory.
• I edited semantic.json file to add only the components like yours.
• I deleted all files inside /dist/components directory. Then, I ran npx gulp build.
• It built the only components that describe in semantic.json file.

If I didn’t delete the components that were previously built, they keep remaining even though they are not in semantic.json file. It’s the same as I specified what components to be installed in the installation setup.

As far as I know, it’s been working like that in all previous versions. Not only 2.8.6. Can you check with your older version like above steps?

Not sure how did you install 2.8.6. Did you specify these components since installation? Or you installed with all components and then edited semantic.json file and then it built only the components but, remove the other components automatically?

@lubber-de Can you confirm that it’s working like that?