I am using bower currently as well as an Angular. One of the plugins I am using (ngTable) has a dependency ~1.2.9
Currently am getting confused one what this actually means.
If I set angular as =1.2.14 this still runs fine but in the output of the command line it mentions 1.2.9 angular as well as .14
Some clarity on this would be greatly appreciated.
My current understand (which may be wrong) is that
= (Means that it will always be that)
> (Means putting 1.2 will allow for the highest of 1.2 until 1.3)
=> (Means equal or more same as above)
But when it comes to >1.2.9 or ~1.2.9 I'm not sure
~1.2.9 means the last patch version starting from 1.2.9.
Update:
So 1.2.9, 1.2.10, 1.2.11... but not 1.3
>1.2.9 means the version must be greater than 1.2.9. 1.3 is OK.
More information on the syntax for dependencies is available on npm site
Related
i recently updated huge project from Scala 2.12 to 2.13 and switched form using
https://github.com/shogowada/scala-json-rpc
to:
https://github.com/nawforce/scala-json-rpc
And few methods - jsonRPCServer.{bindApi, receive} and jsonRPCClient.createAPI - started giving me this error:
value pretty is not a member of io.circe.Printer
It didn't appear in the former version of the library. I tried to examine the sources, but failed to find the problematic calls.
Do, by any chance, any of you had similiar problem?
Looking at Scaladex and looking at the circe dependency for both packages (Scaledex for the original, Scaladex for the fork you are using), it has been upgraded from 0.8.0 to 0.13.0. Looking at this commit it looks like pretty has been deprecated in 0.12.0 (and judging from your post, probably dropped in 0.13.0) and replaced by printWith, which is likely what you want to use.
Allen NLP 0.9.0 (and maybe later) had a pruner module - intended to score and prune spans (https://docs.allennlp.org/v0.9.0/api/allennlp.modules.pruner.html). This seems to have gone missing, I cannot find it in the latest release, or the allennlp-models repo. Is it still part of the library - if not I have the original code so it's no big deal but if it was removed what was the reasoning?
I’m having a problem with printing figures in octave when the figure’s visibility is set to false. For example, the following code produces a “panic: segmentation fault” in Octave version 4.2.2:
t = 1:10;
fh = figure(“visible”, false);
plot(t,sin(t))
print(“fig.png”)
If I run the above code in Octave version 5.2.0, there is no problem. Is this a bug that was fixed in the Octave 5 update? If so, is there a workaround that I can use for Octave 4? I would prefer to use Octave 4 if possible.
Other notes:
I am running this in Ubuntu 16.04.6 LTS and I installed octave 4 using apt.
The answer to your question is, yes. Here is the relevant line from the v5.1.0 NEWS:
Dependencies:
The GUI requires Qt libraries. The minimum Qt4 version supported is Qt4.8. Qt5 of any version is preferred.
The OSMesa library is no longer used. To print invisible figures when using OpenGL graphics, the Qt QOFFSCREENSURFACE feature must be available and you must use the qt graphics toolkit.
Apparently the now deprecated OSMESA dependency and the printing of invisible figures was a long-standing pain-in-the-butt. Maybe you'll have some luck going through bug comments (e.g. someone says that if you make it visible at least once, it may be possible to print).
But as people have said in the comments, the best thing to do would be to upgrade your octave version, and recompile your mexfiles for the new version.
I have not idea about difference in web-component app-layout 2.0.0 and app-layout 2.0.4.
I have build one PWA that use all component with version 2.0.0 in bower.
My query is
Should i update all bower dependency,
Will my PWA performance going to increase after updating
below is version number screenshot.
I have not idea about difference in web-component app-layout 2.0.0 and app-layout 2.0.4.
These are the relevant commits between v2.0.0 and v2.0.4:
2dd9d82 Use different promise polyfill to avoid dep on Polymer 1
17d1d4c Added printer-friendly media queries to app-header-layout and app-drawer-layout
4a1fccc fixes #484
63d5436 Avoid style recalc by reordering operations
2959a53 Wait until attached before setting initial state
a355015 Changed the media query strategy regarding print and has-scrolling-region on app-header-layout
58d536e ensure to multiply by a number
17f1296 (origin/closure) ensure to pass number to cancelAnimationFrame
There might be one performance improvement in 63d5436.
Should i update all bower dependency,
That depends on whether the commits above provide any advantage to you.
Will my PWA performance going to increase after updating
Given the change in 63d5436, which avoids a style recalculation, you may see a rendering performance improvement (i.e., reduced jank, if any) while dragging the app-drawer.
I understand that using ^2.x and ^2.1.2 will both update minor versions and patches as long as major version is still 2, however should I specify minor version and/or patch version if I use the caret?
One of the comments in https://bytearcher.com/articles/semver-explained-why-theres-a-caret-in-my-package-json/ says:
you don't actually want 2.., because that allows both newer and older releases. ^2.1.2 means "2.1.2 or newer".
But if I know ^2.1.2 is already released, wouldn't using ^2.x essentially always be equivalent to ^2.1.2, so is there a purpose to including minor and patch version?
Use this tool to test your hypotheses: https://semver.npmjs.com/
According to this tool, there is a point in including the minor and/or patch version. After experimenting a little bit, it seems that the caret symbol will lock down the minor version but it won't pull in anything that is older than the version you supplied.
So for example: ^2 can pull in version 2.2 but ^2.3 will not.