This is a workflow papercut I'd be happy to remove: native-or-lie@1.0.0 doesn't work in JSPM, but 1.01+ works just fine. Every JSPM install there is a chance that it reinstalls 1.0.0 due to the dependency version in the package.json here and I have to resolve it to use a more recent version with the command: jspm resolve --only npm:native-or-lie@1.0.1 (having force installed 1.0.1 as a direct dependency just to make sure that I always have 1.0.1 installed and that when JSPM reinstalls 1.0.0 I get a warning in its installed forks list. JSPM doesn't seem to have a "permanent resolution" memory.
A fix could be as simple as unpin the 1.0.0 dependency in this library, because it is currently listed in package.json as an explicit pinned dependency. I would have sent a PR directly, but was curious if you had a preferred option to unpin it from 1.0.0: semantic version ^ to allow it to float by minor version; or to keep it pinned, but pin it to 1.0.1 or higher?
This is a workflow papercut I'd be happy to remove:
native-or-lie@1.0.0
doesn't work in JSPM, but 1.01+ works just fine. Every JSPM install there is a chance that it reinstalls 1.0.0 due to the dependency version in the package.json here and I have to resolve it to use a more recent version with the command:jspm resolve --only npm:native-or-lie@1.0.1
(having force installed 1.0.1 as a direct dependency just to make sure that I always have 1.0.1 installed and that when JSPM reinstalls 1.0.0 I get a warning in its installed forks list. JSPM doesn't seem to have a "permanent resolution" memory.A fix could be as simple as unpin the 1.0.0 dependency in this library, because it is currently listed in package.json as an explicit pinned dependency. I would have sent a PR directly, but was curious if you had a preferred option to unpin it from 1.0.0: semantic version
^
to allow it to float by minor version; or to keep it pinned, but pin it to 1.0.1 or higher?