I am deploying my strapi application with render.com and I always run into this problem regarding fontawesome after the command yarn install has run.
it's giving me a 401 unauthorised for a fontawesome free package which shouldn't be happening I don't think.
Render error
I have tried removing yarn.lock and node_modules and locally ran yarn install again but none of it makes a difference every time I push to GitHub and the deploy re-runs.
If you need any more information please let me know!
If you have a solution or can point me in the right direction for one please let me know :) Thank you!
Related
So I was going to work on an Ionic app that I was working on last year and I didn't change anything in framework or anything. So I launch the command "ionic serve" and my app crashes saying a lot of imports don't work like in the picture:
I've tried installing rxjs-compat (even though I haven't updated rxjs) and still doesn't work.
I just did "npm i" just in case something was missing and then launched my app.
Does anyone know what could be the reason that is making everything crash?
Looks like you got unexpected updates.
Please check root directory of your project, if npm i didn't work it means you don't have package-lock.json. If you have it - try to delete node_modules and execute npm install again.
Also check whether yarn.lock is there, then you need to use yarn to install proper packages.
Without yarn.lock and package-lock.json you can only guess suitable versions.
If you remember a date when it worked - try to check which versions were actual then on http://npmjs.com/ and specify them explicitly in the packages.json without ^ or ~ prefix.
I am using React Native and encountered the following error on my android emulator
I am new to React Native and was coding in App.js. I watched a tutorial online on how to use react-navigation so I was following it and created a homestack.js file. My app.js file was still working perfectly fine at this point.
I added code to homestack.js and then imported it to my app.js file but that's when this error popped up. This error was not resolved when I commented out all of the code on homestack.js nor when I commented out the import on my app.js file.
I followed the instructions on the error (clear watchman, delete node modules, yarn install, yarn reset cache) but this also did not resolve the issue.
The fix:
Since none of the above fixed the issue, I removed the homestack.js file from my root folder completely which then fixed the issue. What I did not expect however was that when I put the homestack.js file back into the root folder to see what would happen, the app ran again fine with no issues. It was as if the error never happened.
I guess my question is, what was the actual issue here? Why did taking the file out of the folder and then placing it back in fix the issue? I ran 'npx react-native run-android' after every step of the above fix process so the issue was not because the emulator was running an old version.
Following this error, You have imported react-navigation-stack without install the package. You can install the packge
yarn add react-navigation-stack #react-native-community/masked-view react-native-safe-area-context
or
npm install react-navigation-stack #react-native-community/masked-view react-native-safe-area-context
To know more https://www.npmjs.com/package/react-navigation-stack
After install the package clean project by executing command cd android && gradlew clean, then debug your project.
I'm getting an extremely weird error when trying to npm start my loopback application. I literally did nothing to the code and then this all of a sudden started to happen
Cannot start the application. TypeError: Cannot read property
'definition' of undefined
at getFieldsJsonSchemaFor (/Users/vikramkhemlani/Desktop/loopback/node_modules/#loopback/repository-json-schema/dist/filter-json-schema.js:101:64)
I have the same exact code in another file (which i actually created a git repo from using this repo) but this one is throwing this error for some reason
I went through the same issue.
Apparently there are caches which need to clean up before starting the application. (Expired caches also appear in openapi before I get into this issue)
The project needs to be clean and re-install packages by following:
npm run clean
npm install
I have the same problem.
However, I solved it when I tried the following.
delete node_modules directory.
npm install.
Hello from the LoopBack team 👋
This may be a bug in LoopBack introduced by recent changes. Please create a small application reproducing the problem (see our Bug reporting instructions) and open a new GitHub issue in https://github.com/strongloop/loopback-next/issues/new
Edit:
Summary, I tried to follow only the steps listed in the below two links as applies to windows:
https://github.com/mapbox/mapbox-gl-js/blob/master/CONTRIBUTING.md
https://github.com/stackgl/headless-gl#windows
Here I have reattached the screenshot of the commands that I had problems with:
https://imgur.com/RCQCNU5
One more step I took that I should mention is I also did not find the headless gl when I downloaded the repository, when the install headless gl command did not work I manually copied the file and put it in my local copy under the nodemodules directory thinking it would work but it didnt solve anything. I do think this is related to access issues but I dont know what else I should try to get it working?
First, let's clarify your problem: you want a version of mapbox-gl.js which contains a recently fixed bug.
Your best option is to just wait a couple of weeks for a release.
Failing that, you should build your own, from master. You don't need to set up a debug server for that. You can skip straight to the "Creating a Standalone Build" section.
If the steps for building on Windows don't work for some reason, you could set up a local virtual machine running Ubuntu and use that.
But honestly, just wait a couple of weeks. :)
Just in case some one else need to run this on local server.
After clone
Run npm install
npm run start-debug
It will start listening on port 9966.
Test the debug html files entering to
localhost:9966/debug/FILE_NAME_TO_TEST.html
I keep getting this error in my output when trying to package iOS through Ionic cloud "Error: Registry returned 404 for GET on https://registry.npmjs.org/[MyAppName]". I've followed a few other forum posts that I could find to no avail. Any help would be much appreciated!
in package.json you have [MyAppName] as package or something like that, which when trying to fetch from npmjs.com its not there since you havent publish it, post package.json to check it.
I was using [MyAppName] as a placeholder for my physical app name; for the post. The issue turned out to be the Cordova plugins directory.
To resolve I ran:
ionic state clear --plugins
This, however, resulted in only partial removal of the plugins. I further had to manually delete the rest. Finally I ran:
ionic state restore --plugins
I can build successfully now.