Opened 7 years ago
Closed 7 years ago
#15781 closed enhancement (invalid)
dojo/node needs a build plugin resolver
| Reported by: | Kitson Kelly | Owned by: | Kitson Kelly |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.8.1 |
| Component: | Core | Version: | 1.8.0rc1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Every AMD plugin should have a plugin resolver in util/build/plugins and have it registered in util/build/buildControlDefault. Because this is missing, it causes the following warning when building a custom build:
warn(224) A plugin dependency was encountered but there was no build-time plugin resolver.
Change History (3)
comment:1 Changed 7 years ago by
| Milestone: | tbd → 1.8.1 |
|---|---|
| Owner: | set to Colin Snover |
| Status: | new → assigned |
comment:2 Changed 7 years ago by
| Owner: | changed from Colin Snover to Kitson Kelly |
|---|---|
| Status: | assigned → pending |
comment:3 Changed 7 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Note: See
TracTickets for help on using
tickets.
Server-side builds make no sense since the purpose of the build is to make code smaller for transmission, which is not a concern for SSJS. Since builds ruin debugging, you especially shouldn’t want to do them when you don’t need to.
As far as I can see it does not make sense for me to spend energy on this problem, since “every plugin should have a resolver” is just a generalisation. If you have a specific argument for why this particular plugin should have a build resolver, this can be revisited. Thanks!