npm-install | GitHub Action for install npm dependencies | Continous Integration library

I am working with Hiro Stack.js which I downloaded at https://github.com/hirosystems/stacks.js/tree/master/packages/transaction Also see https://forum.stacks.org/t/stacks-js-error-ts1259-after-npm-install-stacks-network/12929 I am getting an error even when I try to compile a completely commented out .ts file even though "esModuleInterop": true is in tsconfig

This is my (only) tsconfig.json that is located in root of the project.

I am trying to install the required node_modules for a small project running Angular 11 using npm install

My goal is get the project to work locally after downloading it from GitHub. I have already installed the latest version of the Angular CLI. After running the install command I tried npm start.

I was expecting that after running the install and start command to be able to run the project locally. However the actual result I get after running the install command is the following list of errors:

Tell me, I understand that there is a problem in the versions, but how to solve it?

I have tried:

I've been trying to solve this over the last two days, or so, with no effect:

Solution that I have attempted include:

• Deleting the package-lock.json file
• Coordinating with the other dev on the project to align the Node.js version and reinstalling the whole framework
• Using --verbose as part of the "ndm i" command
• Editing environmental variables to add NPM to them
• Deleting the "node_modules" folder
• Disabling, then re-enabling SSH
• Trying with and without VPN being active
• Clearing the cache via the command line, i.e. the node_modules step above

This is a link to another topic on the same issue on SO that also seems to be outstanding: Link

I've reviewed the range of discussions on SO about the problem, to no particular avail, and I think I'm out of options. Any insight is appreciated

I have an Azure (AZ) Function does two things:

1. validate submitted info involving 3rd party packages.
2. when ok call a postgreSQL function at AZ to fetch a small set of data

Testing with Postman, this AF localhost response time < 40 ms. Deployed to Cloud, change URL to AZ, same set of data, took 30 seconds got Status: 500 Internal Server Error.

Did a search, thought this SO might be the case, that I need to bump my subscription to the expensive one to avoid cold start.

But more investigation running part 1 and 2 individually and combined, found:

1. validation part alone runs perfect at AZ, response time < 40ms, just like local, suggests cold start/npm-installation is not an issue.
2. pg function call always long and status: 500 regardless it runs alone or succeeding part 1, no data returned.

Application Insight is enabled and added a Diagnostic settings with:

• FunctionAppLogs and AllMetrics selected
• Send to LogAnalytiscs workspace and Stream to an event hub selected

Following queries found no error/exceptions:

I’m having a problem.
I want to import typescript compiler.
then I tried this command: bit import bit.envs/compilers/typescript --compiler

But it doesn’t worked. This is the error message:

I have an Azure Pipeline configured to build and deploy a .NET 5 application to an on prem server. This works fine for .NET 5, but after upgrading to .NET 6, I had to update the vmImage from windows-latest to windows-2022, as windows-latest doesn't have the .NET 6 SDKs on (according to https://github.com/dotnet/core/issues/6907). This was the error I received

The nuget command failed with exit code(1) and error(C:\Program Files\dotnet\sdk\5.0.404\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets(141,5): error NETSDK1045: The current .NET SDK does not support targeting .NET 6.0. Either target .NET 5.0 or lower, or use a version of the .NET SDK that supports .NET 6.0.

That makes sense, so I've updated the vmImage to windows-2022, and it now gets past that bit, but the pipeline now fails on the webpack task.

Original YAML file (failed on NuGet task due to not having .NET 6 tools available)

I am working with WSL a lot lately because I need some native UNIX tools (and emulators aren't good enough). I noticed that the speed difference when working with NPM/Yarn is incredible.

I conducted a simple test that confirmed my feelings. The test was running npx create-react-app my-test-app and the WSL result was Done in 287.56s. while GitBash finished with Done in 10.46s..

This is not the whole picture, because the perceived time was higher in both cases, but even based on that - there is a big issue somewhere. I just don't know where. The project I'm working on uses tens of libraries and changing even one of them takes minutes instead of seconds.

Is this something that I can fix? If so - where to look for clues?

Additional info:

• my processor: Processor AMD Ryzen 7 5800H with Radeon Graphics, 3201 Mhz, 8 Core(s), 16 Logical Processors

• I'm running Windows 11 with all the latest updates to both the system and the WSL. The chosen system is Ubuntu 20.04

• I've seen some questions that are somewhat similar like 'npm install' extremely slow on Windows, but they don't touch WSL at all (and my pure Windows NPM works fast).

• the issue is not limited to NPM, it's also for Yarn

• another problem that I'm getting is that file watching is not happening (I need to restart the server with every change). In some applications I don't get any errors, sometimes I get the following:

  ...

I have a Phoenix app, in a fresh Windows 10 VM. In this project I cannot run npm install without errors.

After running npm install inside the assets directory I get the following output: