The new version of FontAwesome on npm(v5) - https://www.npmjs.com/package/@fortawesome/fontawesome has a github page that sends users to this project, which is the code for v4.7.0
This is confusing and should be updated.
It looks like this is producing a side-effect of being unable to install v5 of FontAwesome
upon doing
npm i --save @fortawesome/fontawesome
from the examples given here - https://fontawesome.com/how-to-use/use-with-node-js
version 4.7.0 of FontAwesome is installed.
Producing webpack errors of:
Module not found: Error: Can't resolve '@fortawesome/fontawesome-free-solid'
It looks like this is producing a side-effect of being unable to install v5 of FontAwesome
I think this is another issue, by the way the correct title should be "font awesome free repository is not up to date"
@lord-xeon that says that it can't resolve @fortawesome/fontawesome-free-solid
. Have you installed this? Can you share the relevant section of your yarn.lock
, package.json
, or NPM lock file?
@robmadole I have since been able to fix my unresolved errors. I think it was likely because I had missed installing the free-solid
package.
@tagliala I will edit the title to reflect that.
The fix for npm
using the free-*
repos does not work when using bower
as it does not have its own project/repository conceptually but instead directly takes the releases from the corresponding GitHub repo https://github.com/FortAwesome/Font-Awesome.
We'll get the repositories switched over as soon as we can. We aren't going to officially support Bower however as even they are encouraging people to move to NPM or Yarn.
Is there anyway to use v5 without have to download the files by hand?
@odahcam
The docs are confusing as there is no end to end guide that includes installation and usage.
I've already installed free
, free-solid
and free-brands
. But icons are not showing up because it seems like webpack (version 4.12.0) can't resolve the namespaced module for some reason:
Module not found: Error: Can't resolve '@fortawesome/fontawesome' in '/home/tutuca/Proyectos/potaje/assets/js'
Notice how it's trying to resolve inside my assets folder instead of node_modules.
I can correctly reference anything else:
/* Globals */
import '../sass/style.scss';
import { library } from '@fortawesome/fontawesome';
import $ from 'jquery';
import 'bootstrap';
import { viewport, fit } from './helpers';
It's just fontawesome that is breaking. I can post my webpack config but it isn't doing anything fancy.
@tutuca could you please open a new issue, having care to follow our bug report template?
Most helpful comment
@odahcam