Skip to content
This repository was archived by the owner on Oct 2, 2019. It is now read-only.

Outdated NPM version #1148

Closed
Oza94 opened this issue Aug 17, 2015 · 19 comments
Closed

Outdated NPM version #1148

Oza94 opened this issue Aug 17, 2015 · 19 comments

Comments

@Oza94
Copy link

Oza94 commented Aug 17, 2015

The published version on NPM is only 0.11.2, can you please publish 0.12?

My concern is the "postinstall": "bower install" under 0.12 which would force me to install globally bower on my production machines only for ui-select.
@jameskleeh
Copy link

+1

1 similar comment
@chadfawcett
Copy link

+1

@yangliuyu
Copy link

0.12.1 please

@nfleury
Copy link

nfleury commented Aug 22, 2015

+1
pleeaaase

@Oza94 Oza94 changed the title Oudated NPM version Outdated NPM version Aug 22, 2015
@arathael
Copy link

+2 (I have a dude right next to me). He concurs.

@tb
Copy link

tb commented Sep 9, 2015

+1

@mkoryak
Copy link

mkoryak commented Sep 11, 2015

npm publish from project root

@mkoryak
Copy link

mkoryak commented Sep 11, 2015

i forked it and published under a different name:

https://www.npmjs.com/package/ui-select-that-was-forked-solely-to-update-npm-version

@mkoryak mkoryak mentioned this issue Sep 11, 2015
Closed
@eranimo
Copy link

eranimo commented Sep 11, 2015

👏

@jmendiara
Copy link

+1

1 similar comment
@chrisfosterelli
Copy link

+1

@mkoryak
Copy link

mkoryak commented Oct 6, 2015

this is the problem with 500+ open issues. something trivial that will make a lot of peoples lives easier gets ignored for no reason

@lazychino
Copy link

👍 we need this!!

@mkoryak
Copy link

mkoryak commented Oct 16, 2015

npm install ui-select-that-was-forked-solely-to-update-npm-version gets you the latest one, though ill probably delete it when ui-select publishes a new version.. so in a few months

@chrisfosterelli
Copy link

@mkoryak Please consider not deleting the package. Anyone who relies on it may discover suddenly during a deployment that the package is gone with no context. npm recommends against unpublishing packages people depend on.

I'd recommend publishing a patch version containing a deprecation notice in the README and using npm deprecate to mark the package as deprecated.

Thanks for the package by the way!

@mkoryak
Copy link

mkoryak commented Oct 16, 2015

fair enough, ill do that. Glad people found it useful, even with the funny package name :)

@bathos
Copy link

bathos commented Nov 12, 2015

npm version is out of date again, 0.12.100 instead of 0.13.2, which contains big fixes. @mkoryak since this is a recurring issue could we get npm install ui-select-that-was-forked-solely-to-update-npm-version upgraded to 0.13.2?

@mkoryak
Copy link

mkoryak commented Nov 12, 2015

maybe you are looking at the wrong thing, but the npm version is now correct: https://www.npmjs.com/package/ui-select

(it still doesnt have a correct main in package.json though)

aaronroberson added a commit that referenced this issue Jan 25, 2016
@aaronroberson
refactor(commonjs): add support for npm and commonjs
79586aa 
Added ui.select to module exports so that after installing via npm, the package can be required in the angular module dependency list such as:

angular.module('myApp', [require('angular-ui-select')]);

This is helpful for Browserify and Webpack.

Closes #1176 #1148 #692
@wesleycho
Copy link
Contributor

Closing as the current maintainers are publishing to npm.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests