Disable .vscode-server/data/user/history caching - visual-studio-code

i use nextjs in vscode and every time i build my app with
npm run build
the buildId and old build path are saved in .vscode-server/data/user/history I want to disable this because for some reason my nextjs app uses that old info sometimes and changes my new build on itself what results in a 404 error for the buildManifest.js file. This is because it uses the old folder name but the folder has a different name (generated with npm run build). I do this with SSH to my raspberry pi. Let me know! Thanks.

Related

how can i edit heroku app files for discord bots?

I'm stuck at Run error I know how to solve it, I just want to edit app files
like node_modules how I can do such thing?
2021-04-28T15:09:04.098902+00:00 app[worker.1]: /app/node_modules/discord.js/src/client/ClientDataManager.js:81
2021-04-28T15:09:04.098924+00:00 app[worker.1]:guild.channels.set(channel.id, channel);
why do you want to edit a internal file? when you could just simply update to v12.5.3
all the versions below 12.5.3 is broken and is not supported (stage channels broke the versions),
and to your question,
here is what i found while searching ,
"The app’s node_modules directory is generated at build time from the dependencies listed in package.json and the lockfile."
this was from https://devcenter.heroku.com/articles/troubleshooting-node-deploys
So as they are being genarated at the build time, it will not matter of what you change in the node_modules it will not be there when you start your app

App Service deploy of NODE JS app fails with web.config error

I am deploying a NODE JS app to an Azure App Service using Azure Devops pipelines, but it failes with the following error
##[error]Error: Failed to generate web.config. Error: ENOENT: no such file or directory, open 'D:\a\_temp\temp_web_package_09902550774824137\web.config'
But in my deploy step I have the generate web.config step so I am not sure why its not working?
Thanks for asking question! You may try below steps for troubleshooting the issue.
Check that the application is listening on the port provided by the PORT environment variable: process.env.PORT. You may use the WEBSITES_PORT app setting set to port.
Also,review the web.config and make sure the name of the main script file in the handlers section matches the main script file and the Web.config configuration for settings names/values.
Check that the nodeProcessCommandLine setting to ensure that the Node.exe is available at the correction location.
Also, In order for Kudu to detect a Node.js app, you need a package.json file and an app.js/index.js in the root of your folder. It's recommended to correctly set the start script in the package.json file https://docs.npmjs.com/misc/scripts#default-values
If the deployment steps run correctly, however, the app fails to start due to a missing npm package, note that only "dependencies" are installed, "devDependencies" are not installed by default.Try viewing the logs to fetch more details.

Unable to upload package in AEM 6.2 - package file parameter missing

Everytime I upload a package on my QA server via Package Manager, it keeps loading it for a long time and then throws an error saying "package file parameter missing"
The error logs show absolutely no activity regarding the package.
This happens for both code packages (/apps/...) and content packages (/content/...)
Make sure your server has a tmp (linux) or temp (windows) folder accessible to the AEM process with full permission. This error occurs when the aem process cannot find the temp folder which it uses to temporarily store packages when they are being uploaded.

Ionic Starter App testing - www directory not dound

I am new to this platform and I am following the guidelines at the docs. I am trying to test the app using ionic serve CLI response is that there are 3 addresses....I choose localhost and an error comes up - ""www" directory not found. please make sure the working directory is ionic project"
I need help working around this.
I am working on windows 7.
This generally happens when you try to run your project into sub-directory which do not contains ionic project. Verify if you have 'www' folder inside your ionic project or you mistakenly went inside other sub-directory and trying to execute 'ionic serve' command.
After creating you project. The cmd screen will give you the directory of newly created project. Therefore in the CMD type this command:
cd yourprojectname
eg
cd myionicproject
after that command is completed enter command:
$ ionic serve

Play framework 2.0 deployment steps (I think something is missing)

I have some strange problems when I deploy application build with Play framework 2.0. It looks like deployment didn't clean/overwrite compiled files. This I know because one method is changed but still the old is somehow called...
My deployment steps:
in app directory ../play stop
upload all files to app directory from development (except application.conf)
../play clean compile stage
in target directory: ./start -Dhttp.port=80 &
I need some "best practices" advices ;)
Some tips:
Try to use play clean-all instead play clean.
Use the GIT for controlling changes, maybe you forgot to upload something.
Use alternative configuration file for running app in different environments.
Use dist command for building independent production versions, with some bash scripts + git hooks + load balancer you'll be able to switch versions without stopping the application. Anyway remember to move and unzip created file outside the /dist directory, as it is cleaned every time when you call play dist command.