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.
Npm package is missing SimpleLineIcons font.
See original GitHub issueTry executing
npm install react-native-vector-icons@latest --save
Even that npm installs 2.1.0 version, there is no SimpleLineIcons.js file.
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
simple-line-icons - npm
Start using simple-line-icons in your project by running `npm i simple-line-icons`. There are 365 other projects in the npm registry using ...
Read more >Import a npm package (with fonts) from a SASS file
I would like to import simple-line-icons directly as a module and change the prefix $simple-line-icon-prefix to something else.
Read more >simple-line-icons - npm Package Health Analysis - Snyk
Ensure you're using the healthiest npm packages. Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice.
Read more >Getting Font Awesome working with the framework #6477
npm install --save-dev @fortawesome/fontawesome-pro ... build which tells me fontawesome.css is missing and of course no icons display.
Read more >Icon packs for Java applications - Kordamp
It defines a node class named ikonli-font-icon . -fx-icon-code. An icon literal such as di-java or fa-github ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No, issue is not closed. As long as you are going to keep doing this, issue is not closed. By your incompetent actions as maintainer of this library you are wasting our time, just by not wanting to change fucking npm version in one file when you push in master so we know there was un UPDATE!
Wow you sure are entitled. Consider that I’m very busy and was up until 2.30 AM to get this release out. You sir are wasting my time and I don’t get why you are complaining and being abusive now that I just fixed your problem.