I'm just dipping my toes into JHipster and I'm finding that I'm getting lots of warnings upon generating a new project. They all seem to center around this "source-map" item.
warning Resolution field "source-map#0.6.1" is incompatible with requested version "source-map#^0.5.6"
I'm getting 27 lines of warnings with differing version numbers.
The project still builds successfully and runs.
What is going on here?
TY
This is how yarn/npm resolve version conflicts between transitive dependencies, see doc on dependency versioning
Some dependencies require an old version of source-map package but JHipster team has found that only 0.6.1 works (see issue) so they forced it in package.json in resolutions property until the other project release a new version. Yarn applies the resolution but complains because according to semantic versioning rules version 0.6.1 could break dependencies that require ^0.5.6 but it's only a guess.
You can find what's going on in details by inspecting yarn.lock and looking for source-map.
Related
So I was building out a test APK in Android Studio tonight that had to be signed. It failed and said my Gradle was out of date. So I upgraded my gradle from 7.3.3 to the newest 7.5.1
I changed the wrapper setting to distributionUrl=https\://services.gradle.org/distributions/gradle-7.5.1-all.zip
and then I changed my build.gradle dependency to classpath 'com.android.tools.build:gradle:7.5.1'
Note that after doing the changes, and restarting Android Studio, it did upgrade the version in the app directory.
Here's the error getting thrown below:
* What went wrong:
A problem occurred configuring root project 'android'.
> Could not resolve all files for configuration ':classpath'.
> Could not find com.android.tools.build:gradle:7.5.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/7.5.1/gradle-7.5.1.pom
- https://repo.maven.apache.org/maven2/com/android/tools/build/gradle/7.5.1/gradle-7.5.1.pom
Required by:
project :
Note that this was a project from a client, and I did not write this originally. These dependencies were in place, but fairly recent, and the app would build fine with it using 7.3.3. However it wouldn't let me sign my app.
I suppose I could use some wisdom on both of these issues. What I'm going to do is go back to version 7.3.3, build the signed APK again, and copy that exact error to report back here with. It was a gradle version error.
For any any Flutter noobs like myself passing through, this error occured because the Android Tools Plugin version DOES NOT match the Gradle Version:
https://developer.android.com/studio/releases/gradle-plugin#groovy
They match up just vaguely enough in number, that you would think that my line com.android.tools.build:gradle:7.5.1. uses gradle 7.5.1, but instead, Android Tools for Gradle is actually a separate entity, and at 7.3.3 as of typing this reply.
So you CAN set your Gradle to the newest version somewhere else in your project, but it has to match the compatible Android Tools version, which is set here. Its silly and confusing at first, and can easily trip up newcomers. Hopefully the versions diverge enough, or the code syntax changes for some better clarity, but as of now, this is it.
I am trying to set up packages for a WinForms XAF XPO Standard Security Application.
I used the wizard to create the solution.
Then the project updater
Then I edited the project file package references.
However when I try to build the .exe project I get
NU1101 Unable to find package DevExpress.ExpressApp.Persistent.Base. No packages exist with this id in source(s):
Even though the package shows in the references.
I tried checking the installed packages
For some reason DevExpress.ExpressApp.Persistent.Base was showing in Package Manager as installed in the Module.Win project.
I removed it and now I can build the solution.
Antler lists StackOverflow as its support site. So here's my support question. When I attempt to install the ANTLR 4 parser generator package, Antlr4 specifically, for Visual Studio 2010+ projects (version 4.5.3.1-beta001) via NuGet 2.8.60318.667, I get the following error:
Attempting to resolve dependency 'Antlr4.CodeGenerator (≥ 4.5.3.1-beta001)'.
External packages cannot depend on packages that target projects.
How do I work around this and get the ANTLR code generator installed?
As of at least version 4.5.3.1-beta001, generating C# with ANTLR 4 requires two NuGet packages: Antlr4.Runtime and Antlr4.CodeGenerator. Another package, Antlr4 depends on these two. Presently, attempting to install Antlr4 throws the error in the question above. However, if you install Antlr4.Runtime and then Antlr4.CodeGenerator, the install will work fine.
I am getting following error once i run the project in visual studio 2012.
Warning 1 Some NuGet packages were installed using a target framework
different from the current target framework and may need to be
reinstalled. Visit
http://docs.nuget.org/docs/workflows/reinstalling-packages for more
information. Packages affected: Microsoft.Web.Infrastructure,
SignalR.Hosting.AspNet, SignalR.Server
Reinstalling packages seem pretty straightforward. But, it can get very tricky since the following may affect or be affected by it:
Project retargeting or project upgrade where the target framework of the project gets changed Package dependencies and their versionsDependent packages and their versions.
I suggest you should read this document.
https://docs.nuget.org/consume/reinstalling-packages
read When to Reinstall Packages and What to Watch for section.
I updated Xamarin Mvvmcross 3.2.2 project to 3.5 for Unified API support.
Mvvmcross.HotTuna 3.5 package is added in project.
So there are Mvvmcross.HotTuna.CrossCore and Mvvmcross.HotTuna.MvvmCrossLibraries packages can be seen under Package folder.
But cannot find binding assemble, so "using Cirrious.MvvmCross.Binding;" is not resolved.
And MvxTouchSetup is also not resolved
The project worked well with Mvvmcross3.2.2.
Now what other nuget packages should be added in the project?
No package is added newly.
The 3.5 libraries package has been updated to include the new MvvmCross.Touch.dll for lib\Xamarin.iOS10\ - see https://github.com/MvvmCross/MvvmCross/blob/3.5/nuspec/MvvmCross.HotTuna.MvvmCrossLibraries.3.0.1.nuspec#L72
The 3.5 crosscore package has bee update to include the new MvvmCross.Binding.Touch.dll for lib\Xamarin.iOS10\ - see https://github.com/MvvmCross/MvvmCross/blob/3.5/nuspec/MvvmCross.HotTuna.CrossCore.3.0.1.nuspec#L91
If the update isn't working for you:
read the advice on http://kerry.lothrop.de/unified-api-for-xamarin-ios/ about how to update the unified
check you have updated your own project to Xamarin iOS unified
check you have up-to-date nuget installed
clean, rebuild, swear and retry until it all works