Opened 10 years ago
Closed 10 years ago
#14663 closed feature (fixed)
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?
Change History (4)
comment:1 Changed 10 years ago by
| Owner: | set to braddunbar |
|---|---|
| Status: | new → pending |
comment:2 Changed 10 years ago by
| Status: | pending → new |
|---|
That's correct. I would like to use browserify with jQuery 1.11.0.
comment:3 Changed 10 years ago by
| 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.
comment:4 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
Note: See
TracTickets for help on using
tickets.
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?