Error using karma-browserify with browserify-shim - gulp

I'm trying to use karma-browserify together with browserify-shim with no success. Here is a repo to reproduce the error: https://github.com/pelizza/karma-browserify-shim
PhantomJS 2.1.1 (Mac OS X 0.0.0) ERROR
TypeError: undefined is not an object (evaluating 'module.exports = ex')
at /var/folders/_0/ql88mbyd6v34qsmysr5kf4780000gn/T/e0c5e5ebe3f49930de3d988c7196737f.browserify:40308 <- bower_components/jquery/dist/jquery.js:9837:0
Everything works fine when bundling with browserify, by it seems that karma simply doesn't find shimmed dependencies when preprocessing files with karma-browserify.
I couldn't find much about this problem, except this one at stack overflow, without a solution: karma-browserify throws error when trying to load modules shimmed with browserify-shim

Found the solution: just remove the browserify-shim transform from the karma configuration file if it was already declared as a transform on package.json.
I have updated the repo with this fix.
Here is the discussion about this issue: https://github.com/nikku/karma-browserify/issues/170#issuecomment-187372309

Related

Webpack 5 - ERROR in Error: Child compilation failed: Module parse failed: Unexpected character '�' (1:4)

I don't understand what is the problem? Webpack does not compile the project and shows the following error:
ERROR in Error: Child compilation failed: Module parse failed: Unexpected character '�' (1:4)
But I can't figure out where the error derives from, in which module or file, where to look for it? This is the error from my IDE.
At the moment, it gives only 1 error when compiling, before that there were 22 errors. Actions that could lead to this - trying to solve the problem through CSS.
After I removed everything in the code (-webkit-min-device-pixel-ratio: 2), the number of errors was reduced to 1, but I don’t understand what to do next.
My webpack 5 config: webpack.config
If someone knows how to solve this problem, or where to look for the root of evil, please help.
Problem solved! It turned out that in my webpack.config in the image processor, I did not add webp support. And when I added it on the fly, the already assembled project did not take this moment into account. As a result, after restarting the build with the npm run dev command, the updated webpack config file started working as it should! Thank you all for your attention to the issue and the desire to help figure it out! enter image description here

upgraded to latest nx workspace, test fail with transform

We are upgrading angular with nx workspace to latest
The problem is when we run test, we got following errors
feature-flag.mjs:93:20: ERROR: Transforming for-await loops to the configured target environment ("es2015") is not supported yet
feature-flag.mjs:184:4: ERROR: Transforming async generator functions to the configured target environment ("es2015") is not supported yet
The feature-flag library was build es2020, and our current App also on es2020 after upgrade.
The app using the feature-flag lib test fails with the error
I am not sure how to fix it
Things I have tried, in the App I have adjust tsconfig, tsconfig.app, tsconfig.spec to es2015 or es2017, but it didn't help.

Package error IOS_13 on Windows platform only

I just updated the project to 5.0 from 5.0EA. While in editor everything runs fine but I tried to package it for some testing, and I’m getting the following error, even tho in Project Settings I only have checked Windows as platform. I wasn’t getting this error before, is there something I’m missing?
LogClass: Warning: In asset ‘None’, there is an enum property of type ‘EIOSVersion’ with an invalid value of ‘IOS_13’
LogObj: Error: LoadConfig (/Script/IOSRuntimeSettings.Default__IOSRuntimeSettings): import failed for MinimumiOSVersion in: IOS_13
I uninstalled UE5 and then removed all of it's files from AppData, reinstalled it and the problem is gone. I don't know why it was trying to use IOS too even tho it wasn't checked but at least that was the solution for me. Just uninstalling are reinstalling wasn't enough.

java.lang.NoSuchFieldError: defaultReader (JsonSmartJsonProvider.java:39)

I am using json-path-2.4.0 library in spark jobs which has a dependency on json-smart 2.x , but the spark jars default classpath folder (/usr/hdp/2.6.5.0-292/spark2/jars/) has json-smart 1.x which always gets precedence and I am unable to use the json-path 2.x library.
Facing the below error everytime I run :
java.lang.NoSuchFieldError: defaultReader
at com.jayway.jsonpath.spi.json.JsonSmartJsonProvider.(JsonSmartJsonProvider.java:39)
at com.jayway.jsonpath.internal.DefaultsImpl.jsonProvider(DefaultsImpl.java:21)
at com.jayway.jsonpath.Configuration.defaultConfiguration(Configuration.java:174)
Similar issue has been reported earlier :
JSON Path 2.3.0 conflicts with hadoop 2.7 Environment JSON-smart1.2.0.jar
But havent found any working solution. Please help.

The "GenerateDepsFile" task failed unexpectedly

I tried to compile my new application in MonoDevelop and I got this error:
/usr/share/dotnet/sdk/2.2.203/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.targets(5,5): Error MSB4018: The "GenerateDepsFile" task failed unexpectedly.
System.TypeLoadException: Could not load type of field 'Microsoft.NET.Build.Tasks.DependencyContextBuilder:_filteredPackages'
(12) due to: Could not resolve type with token 01000027 from typeref
(expected class 'NuGet.Packaging.Core.PackageIdentity' in assembly
'NuGet.Packaging, Version=5.0.0.6, Culture=neutral,
PublicKeyToken=31bf3856ad364e35') assembly:NuGet.Packaging,
Version=5.0.0.6, Culture=neutral, PublicKeyToken=31bf3856ad364e35
type:NuGet.Packaging.Core.PackageIdentity member:(null)
at Microsoft.NET.Build.Tasks.TaskBase.Execute () [0x00000] in :0
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute
() [0x00029] in <58f0218f988743a48dd7c84cbe933f4e>:0
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask (Microsoft.Build.BackEnd.ITaskExecutionHost taskExecutionHost,
Microsoft.Build.BackEnd.Logging.TaskLoggingContext taskLoggingContext,
Microsoft.Build.BackEnd.TaskHost taskHost,
Microsoft.Build.BackEnd.ItemBucket bucket,
Microsoft.Build.BackEnd.TaskExecutionMode howToExecuteTask) [0x001f6]
in <58f0218f988743a48dd7c84cbe933f4e>:0 (MSB4018) (passcracker)
I cannot compile any application. Please help.
I had the same problem using .Net Standard 2.1, and I solved it for myself by cleaning the solution and then rebuilding it.
Just moved my projects to a new machine (copying, not pulling from GIT) and started getting this. Deleting the bin and obj folders in each project solved this issue.
Your combination of Mono MSBuild and .NET Core SDK is incompatible because they use different versions of the internal NuGet library. To resolve this problem, you can:
Downgrade .NET Core SDK to 2.1.5xx or 2.2.1xx (for example, 2.1.505 or 2.2.108)
Upgrade Mono to 6.0
You can find a detailed explanation of this problem and possible solutions here: https://rider-support.jetbrains.com/hc/en-us/articles/360004180039
This appears to be a known issue.
The only fix at this stage seems to be to downgrade to .NET Core v2.2.105.
To downgrade:
Uninstall the latest .NET Core version (v2.2.2+).
Download and install v2.2.105.
Run the following CMD in the *.sln folder. This will delete all your OBJ and BIN folders automatically. And your issue will be solved.
FOR /d /r . %%d in (bin,obj) DO ( IF EXIST "%%d" ( ECHO %%d | FIND /I "\node_modules\" > Nul && ( ECHO.Skipping: %%d ) || ( ECHO.Deleting: %%d rd /s/q "%%d" )))
I had the same problem in migration from .Net Framework 4.5 to .NET 6.0 (with the 70 project).
All of the above answers are correct, but they were not enough for my problem.
I use this answer:
Deleting the bin and obj and .vs folders then Clean Solution and
Rebuild Solution
it's working in Build Mode, not Rebuild. And the problem remained.
I update the Version of SDK , but not enough and I have the problem.
I realized this:
duplicate property (or variables) with the same name (or similar Name) in derived classes.
It was a good solution and a few problems were solved.
finally (after the 3 days), The biggest problem I noticed was that I had Loop References.
I fixed The Loop References in projects and the error is solved.
Change the name of the file. For instance, Add prefix _ or #; so, it cannot be used.
Restart Visual Studio, then try to build. If still problem is there, needs to restart the machine.
I had this error happen and the slove for me was correcting the Package version number in .csproj file .
<Version>2.0.7.</Version> <!--casued the error-->
<Version>2.0.7</Version> <!--this fixed the error-->
Removing the trailing '.' fixed this for me.
I had .net standard project built on .net standard 2.0. Yesterday I updated my Visual Studio 2019 to 16.3.0 to leverage .Net Core 3.0. But all of sudden build of project targeting on standard 2.0 started throwing "GenerateDepsFile" task failed unexpectedly error.
I was able to resolve this issue by changing the target framework to 2.1.
If you have <DelaySign>false</DelaySign> in your .csproj file remove it to solve this Problem.
in vs code i got this error, after trying some solution from forms, i found solution in deleting bin and obj foldersfrom project and build again.
this solved my problem.
vs code version: 1.53.1
dotnet version : 5
I had it after updating vs 2019 community,
Delete bin & obj folders,
then clean & build the solution.
I had this error and after reading comments, I was able to resolve by combining comments - First deleted bin folder, obj folder, executed clean command, deleted enter image description here and then rebuilded.