Inconsistently named installs with bower about ftdomdelegate HOT 6 CLOSED

Looks like the package was registered in Bower as dom-delegate. I've no idea how bower install ftdomdelegate was finding it. I've registered ftdomdelegate, and I'll update the name in bower.json.

from ftdomdelegate.

Findings:

1. Older versions of Bower (circa 1.3) put bower install ftdomdelegate in bower_components/ftdomdelegate. Recent versions put it in bower_components/dom-delegate (the name from bower.json.
2. I have no idea how Bower's resolving ftdomdelegate; it's not registered in that name.
3. Packages shouldn't be doing bower install --save ftdomdelegate, because the package shouldn't exist under that name.

2 seems like a Bower issue. 3 is something we should fix in o-share etc.

from ftdomdelegate.

2 - ftdomdelegate is in the origami regsitry
3 - we decided that within ft ftdomdelegate should be the canonical name
(see the issue linked to above). Unfortunately we need to support
dom-delegate too as that's the name it was publicly published as first

On 5 January 2016 at 12:04, Matt Brennan [email protected] wrote:

Findings:

1. Older versions of Bower (circa 1.3) put bower install ftdomdelegate
   in bower_components/ftdomdelegate. Recent versions put it in
   bower_components/dom-delegate (the name from bower.json.
2. I have no idea how Bower's resolving ftdomdelegate; it's not
   registered in that name.
3. Packages shouldn't be doing bower install --save ftdomdelegate,
   because the package shouldn't exist under that name.

2 seems like a Bower issue. 3 is something we should fix in o-share etc.

—
Reply to this email directly or view it on GitHub
#77 (comment)
.

This email was sent by a company owned by Financial Times Group Limited
("FT Group http://aboutus.ft.com/corporate-information/#axzz3rajCSIAt"),
registered office at Number One Southwark Bridge, London SE1 9HL.
Registered in England and Wales with company number 879531. This e-mail may
contain confidential information. If you are not the intended recipient,
please notify the sender immediately, delete all copies and do not
distribute it further. It could also contain personal views which are not
necessarily those of the FT Group. We may monitor outgoing or
incoming emails as permitted by law.

from ftdomdelegate.

Aha, gotcha. So at a guess it's not the repo name but the fact that the name in o-share's dependencies is different to the name in bower.json. I'm putting together a test case to verify.

from ftdomdelegate.

Test case: https://github.com/quarterto/quartertobowertest-dep. It's definitely the difference between the dependencies key and the bower.json name. It's worth noting that bower install --save ftdomdelegate would add it to dependencies as an alias to dom-delegate:

"dependencies": {
  "dom-delegate": "ftdomdelegate#^2.0.0"
}

I'll report to Bower.

from ftdomdelegate.

v3 renames to ftdomdelegate

from ftdomdelegate.