I'm attempting to build a SvelteKit that deploys with Cloudflare using this adaptor https://kit.svelte.dev/docs/adapter-cloudflare
However when I run "CF_PAGES=1 vite build" I get the following error "'CF_PAGES' is not recognized as an internal or external command,
operable program or batch file."
I suspect I may be missing an environment variable.
The cause is that you are attempting to run the UNIX command on Microsoft Windows.
Potential solutions
Translate UNIX command syntax of setting environment variables to Microsoft Windows command syntax. See here how to set environment variables on Windows
Use a UNIX based workflow on Microsoft Windows, like WSL2 or Docker containers
Related
We are using the remote-ssh extension to run VS Code locally on MacOS and remotely connecting to our code repo on Linux. This part works fine. But now I'm installing a custom extension (that we developed) that requires the JAVA_HOME environment variable to be set on the remote Linux host where the extension runs. I've tried a number of things, but I can't find the right way to set this environment variable in this remote-ssh flow.
I understand the VS Code Server is being run on the remote machine to enable the remote-ssh flow. Is there a way to set my required environment variable on the VS Code Server instance so that my extension sees it?
The direnv extension will do that, but you'll have to have direnv installed on the remote and have .envrc like this:
export JAVA_HOME=...
I have install loopback 4 framework in my system by this command npm i -g #loopback/cli. But after installation by terminal I, can't create loopback application because it showing lb4 command not found. I also search through web and do many changes in environment variables but got same problem. I have executed this command with different terminal and same problem is getting.
I have attachments which will help you to understand the problem
I am running this command on command prompt in windows 10 system
This can occur for several reasons; Typically, it's caused by a misconfigured PATH variable or a stale "cache" of the terminal. A quick solution is to use npx #loopback/cli instead.
Runing the Build and Run Iot Edge Solution in Simulator stopped working suddenly, and the log builds the containers and stops at this message Network azure-iot-edge-dev is external, skipping Everything was working fine 5mins ago, tried rebooting, restarting docker, iotedgehubdev, but in vain. Do you know how can I get more logs and/or resolve this problem ?
This is a generic error that is thrown for a variety of reasons.
Possible causes can be:
Proxy blocking pulling images of edgeHub and edgeAgent
A problem in the deployment.template.json (or debug template), e.g. missing brackets
Ports of edgeHub that are in use
Docker configured for Windows containers when targeting Linux or visa-versa
The Build output or IoT hub output in Visual Studio usually gives a bit more information.
Do you know how can I get more logs and/or resolve this problem ?
Are you trying to debug/simulate it locally on windows 10 machine?
When you need to gather logs from an IoT Edge device, the most convenient way is to use the support-bundle command. By default, this command collects module, IoT Edge security manager and container engine logs, iotedge check JSON output, and other useful debug information. It compresses them into a single file for easy sharing. The support-bundle command is available in release 1.0.9 and later.
Run the support-bundle command with the --since flag to specify how long from the past you want to get logs. For example 6h will get logs since the last six hours, 6d since the last six days, 6m since the last six minutes and so on. Include the --help flag to see a complete list of options.
sudo iotedge support-bundle --since 6h
By default, the support-bundle command creates a zip file called support_bundle.zip in the directory where the command is called. Use the flag --output to specify a different path or file name for the output.
Incase if you are looking to debug the modules locally on VS2019, VS Code below documentations will be useful.
Use Visual Studio 2019 to develop and debug modules for Azure IoT Edge and
Use Visual Studio Code to develop and debug modules for Azure IoT Edge
Please share the complete logs if the above doesn't help.
I have this issue when trying to start a project from within Visual Studio when it's not running in administrator mode. I always forget and end up with this error. Same goes for if I run "iotedgehubdev.exe setup" from a command prompt. It only works when the command prompt is running in administrator mode.
ERROR in ./services/emailService.js
Module not found: Error: Can't resolve '#/apis/adl/instance/EmailsApi' in
I'm getting this error when running the nuxt build inside docker container or in some CI/CD server like code build. this works properly in my local machine. I'm using mac. anyone can help?
If it work fine locally its most likely because of case sensitivity. CI/CD usually run on linux, and usual filesystem on linux is case dependent.
While MacOs usually run on case-insensitive file system. So your file is found on Mac, but not on linux because its in different case
I am trying to put sample for MFP-8.0 Apps and i follow that below links & video,
https://mobilefirstplatform.ibmcloud.com/blog/2016/06/17/ibm-mobilefirst-studio-8-0-plugin-for-eclipse-now-available/
This is error message i got from eclipse console.
E:\POC\MFP-8.0\MFP\SampleTest\www>mfpdev app register --noprompt
E:\POC\MFP-8.0\MFP\SampleTest\www>exit
'mfpdev' is not recognized as an internal or external command,
operable program or batch file.
If anything i missed out for above the tutorial what else i have to do? kindly any one advice me.
System environment : Windows 8.1,Eclipse Mars, Java 1.8
Thanks
If it doesn't know what "mfpdev" is, it sounds like then that you do not have the MobileFirst CLI installed.
Make sure you have nodejs installed, then from command line run the following command: npm install -g mfpdev-cli, which will install the CLI.
The Studio plug-in relies on the CLI installed, since behind-the-scenes it calls CLI commands.