Side navigation
#14663 closed feature (fixed)
Opened January 02, 2014 03:14PM UTC
Closed January 23, 2014 04:02PM UTC
jQuery 1.11.0-beta3 on npm
| Reported by: | braddunbar | Owned by: | braddunbar |
|---|---|---|---|
| Priority: | high | Milestone: | 1.11 |
| Component: | build | Version: | 1.11.0-beta2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
While jQuery 2.1.0-beta3 was published on npm (thanks much), 1.11.0-beta3 was not. Could we get it published as well? If not, what are the reasons?
Attachments (0)
Change History (4)
Changed January 02, 2014 03:28PM UTC by comment:1
| owner: | → braddunbar |
|---|---|
| status: | new → pending |
Changed January 02, 2014 03:35PM UTC by comment:2
| status: | pending → new |
|---|
That's correct. I would like to use browserify with jQuery 1.11.0.
Changed January 05, 2014 02:18AM UTC by comment:3
| component: | unfiled → build |
|---|---|
| milestone: | None → 1.11 |
| priority: | undecided → high |
| status: | new → open |
We'll need to figure out how to explain that we publish 1.x on npm but don't support it on node.
Changed January 23, 2014 04:02PM UTC by comment:4
| resolution: | → fixed |
|---|---|
| status: | open → closed |
We're not encouraging anyone to use 1.x with node. I'm assuming you want to use npm as your package manager but not use node? Can you describe the use case? Browserify?