-
Notifications
You must be signed in to change notification settings - Fork 96
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
npm install failing #11
Comments
@abdullahsumbal Just tried the same. Changing the fontnik version did not work for me. Still have an error :(
|
@georgbachmann, I just recloned and did npm install again. It works for me. Which operating system are you using? I have a Ubuntu 16.04.6 LTS system with node v10.16.3 and npm v6.9.0. |
I am on MacOS 10.14.6. Node V12.9.1 and npm 6.10.3 |
Hey @georgbachmann, I dont have a Mac, so I can not test it. If you just need the generated fonts from this repo. I have put the generated fonts on this link https://abdullahsumbal.com/Doc/fonts.zip |
@abdullahsumbal Thanks for your help, but I'd need my own fonts unfortunately... |
Running My npm-foo isn't great so I've not the faintest clue why it can't just resolve the package from the |
openmaptiles/font uses fontnik. fontnik installs only with supported node versions. See https://github.com/mapbox/node-fontnik/blob/master/README.md for a list of supported node versions. Build from source does not work because of a missing C++ flag somewhere I was able to solve the problem by switching to node version 6.17.1:
|
For the benefit of anyone trying to do this on a Mac... just don't. Spent way too many hours on it this afternoon. I've installed it on an Ubuntu 16.04 VM and it works fine using @anneb's version suggestion. |
It worked flawlessly for me on macOS Big Sur 11.2.3 and Node v14.15.4. |
after cloning the repo, npm install throws this error for me: "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(24 On Win 10, Node v16.7 I have installed Visual Studio 2019 (some basic stuff for C++) and "Microsoft.CppCommon.targets" does exist in that directory... but it's still throwing an error. Thoughts? I'm sure there are others that have run into this... |
Nevermind. Found a different solution. For anyone looking to find an online conversion from a regular font (.TTF for example) to PBF, just use: Hope that's helpful. |
I got this error message when running
npm install
Changing npm package
fontnik
version tov0.5.3
in thepackage.json
fixed the problem for me.The text was updated successfully, but these errors were encountered: