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.

Error when adding a directory to embark.json

See original GitHub issue

I am trying to add a fonts directory to the embark.json file and followed one of the issues as an example.

My embark.json entry is this: "css/fonts": ["app/css/dist/themes/default/assets/fonts/**"],

and the error I am getting is this: ENOENT: no such file or directory, stat 'dist/css/fonts/css/dist/themes/default/assets/fonts/icons.eot'

seems like embark is concatenating the target directory specified and the source directory after dropping ‘app/’ and trying to copy that as the file path. I tried making changes to pipeline.js to test, but couldn’t find the tasks folder to re-build with grunt.

Issue Analytics

State:
Created 7 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

toadkickercommented, Mar 15, 2017

Confirmed issues:

    "fonts/**": ["app/fonts/**"]

returns

Error: ENOENT: no such file or directory, stat 'dist/fonts/**/fonts/alexbrush-regular-webfont.woff'
    at Error (native)
    at Object.fs.statSync (fs.js:987:18)
    at Object.statSync (/Users/toadkicker/.nvm/versions/node/v6.9.4/lib/node_modules/embark/node_modules/graceful-fs/polyfills.js:297:22)
    at Function.copySync (/Users/toadkicker/.nvm/versions/node/v6.9.4/lib/node_modules/embark/node_modules/fs-extra/lib/copy-sync/copy-sync.js:29:84)
    at Object.copySync (/Users/toadkicker/.nvm/versions/node/v6.9.4/lib/node_modules/embark/lib/core/fs.js:9:22)
    at /Users/toadkicker/.nvm/versions/node/v6.9.4/lib/node_modules/embark/lib/pipeline/pipeline.js:66:12
    at Array.map (native)
    at Pipeline.build (/Users/toadkicker/.nvm/versions/node/v6.9.4/lib/node_modules/embark/lib/pipeline/pipeline.js:61:20)
    at EventEmitter.<anonymous> (/Users/toadkicker/.nvm/versions/node/v6.9.4/lib/node_modules/embark/lib/core/engine.js:76:14)
    at emitOne (events.js:96:13)

Work Around

Declare each file needed and skip the globbing code in pipeline.js

    "fonts/stylesheet.css": ["app/fonts/stylesheet.css"],
    "fonts/alexbrush-regular-webfont.woff": ["app/fonts/alexbrush-regular-webfont.woff"],
    "fonts/alexbrush-regular-webfont.woff2": ["app/fonts/alexbrush-regular-webfont.woff2"]

@iurimatias I’m lobbying to just remove this pipeline entirely from the framework and make it a plugin all its own. There are too many concerns with serving up front end code that are already solved elsewhere. Plus developers are opinionated about what template libraries and such to use, and embark shouldn’t decide that stuff for them. It would be better to offer some default choices that can be easily swapped out via plugins vs letting the framework get in the way of seeing UI.

0reactions

iurimatiascommented, Jun 22, 2018

Closing as this has been fixed for a while now.

Top Results From Across the Web

embark-framework/Lobby - Gitter

Error Compiling/Building contracts: Solidity errors: Unknown exception during compilation. ... I had solc 0.5.9 installed but 0.5.8 specified in embark.json.

0 - Stack Overflow

json , else just want to create this json file into the alexadata folder. But both of two status, I have an error...

embark/README.md at master - vyper - GitHub

Add the embark-vyper plugin to embark.json : ... Next, let's create a Vyper contract in the contracts folder of our ÐApp, ... Error...

Embark Documentation - Read the Docs

The option can be configured at config/blockchain.json. ... flexible and you can configure you're own directory structure using embark.json.

Configuring Embark

Every application created with Embark comes with an embark.json file. ... The default name of this directory is embarkArtifacts .