Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning: Unable to read "node_modules/font-awesome/fonts/fontawesome-webfont.*" #1038

Closed
gustawdaniel opened this issue Nov 18, 2018 · 4 comments

Comments

@gustawdaniel
Copy link

I am on branch develop. I run

./node_modules/.bin/grunt dev

with logs

>> Local Npm module "grunt-appdmg" not found. Is it installed?

Running "gitinfo" task

Running "clean:dist" (clean) task
>> 0 paths cleaned.

Running "clean:desktop" (clean) task
>> 0 paths cleaned.

Running "clean:cordova" (clean) task
>> 0 paths cleaned.

Running "eslint:app" (eslint) task

Running "eslint:desktop" (eslint) task

Running "eslint:grunt" (eslint) task

Running "copy:html" (copy) task
Copied 1 file

Running "copy:favicon" (copy) task
Copied 1 file

Running "copy:icons" (copy) task
Copied 10 files

Running "copy:manifest" (copy) task
Copied 2 files

Running "copy:fonts" (copy) task
Warning: Unable to read "node_modules/font-awesome/fonts/fontawesome-webfont.*" file (Error code: ENOENT). Use --force to continue.

Aborted due to warnings.


Execution Time (2018-11-18 02:32:57 UTC+1)
loading tasks    2.6s  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 29%
gitinfo         115ms  ▇ 1%
eslint:app       6.1s  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 66%
eslint:desktop  106ms  ▇ 1%
eslint:grunt    242ms  ▇▇ 3%
Total 9.2s

Most important is

Warning: Unable to read "node_modules/font-awesome/fonts/fontawesome-webfont.*" file (Error code: ENOENT). Use --force to continue.

Problem is described there:

webpack-contrib/less-loader#53

but in my case this was because of lacking font-awesome in node_modules...

I fixed by

npm i font-awesome --save-dev
@gustawdaniel
Copy link
Author

But is is strange because of font-awesome is in dependencies.

@gustawdaniel
Copy link
Author

I see thatn npm i change a lot of things in package-lock.json it is connected with

npm/npm#20434

Is there any recommended version of node and npm to develop this project?

@gustawdaniel gustawdaniel reopened this Nov 18, 2018
@gustawdaniel
Copy link
Author

Example of changes

       "requires": {
-        "micromatch": "2.3.11",
-        "normalize-path": "2.1.1"
+        "micromatch": "^2.1.5",
+        "normalize-path": "^2.0.0"
       }

or

       "integrity": "sha1-DNkKVhCT810KmSVsIrcGlDP60Rc=",
       "dev": true,
       "requires": {
-        "kind-of": "3.2.2",
-        "longest": "1.0.1",
-        "repeat-string": "1.6.1"
+        "kind-of": "^3.0.2",
+        "longest": "^1.0.1",
+        "repeat-string": "^1.5.2"
       }
     },

@gustawdaniel
Copy link
Author

I had

node -v
v8.11.1
npm -v
6.4.1

I updated

Now using node v10.7.0 (npm v6.1.0)

Than I had error:

sass/node-sass#1764

I fixed by removing node_modules and npm install.

but problem is still present.

I tried npm update

Only success that there is small amount of vulnerabilities

Before update

audited 8295 packages in 21.476s
found 60 vulnerabilities (17 low, 20 moderate, 20 high, 3 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

After update

s and audited 12347 packages in 72.15s
found 46 vulnerabilities (16 low, 16 moderate, 13 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

S I hope I do not broke nothing by this update. Anyway

./node_modules/.bin/grunt dev

does not works because of error

Running "sign-html:app" (sign-html) task
Warning: Error signing app html. To build without sign, please launch grunt with --skip-sign. Use --force to continue.

Aborted due to warnings.

so I will try

./node_modules/.bin/grunt dev --skip-sign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant