can-connect
or is that overkill? If so, what is recommended? can-ajax
? something else? thanks.
can-construct
with some functions that call can-ajax
or $.ajax
Error: Error loading "can-globals@0.3.0#is-web-worker/is-web-worker" at http://localhost:63342/Shuttle.Access.Site/node_modules/can-globals/is-web-worker/is-web-worker.js
can-globals
in the working project has the /is-web-worker/
folder yet the other does not
npm ls can-globals
+-- can-component@4.0.4
| +-- can-control@4.0.2
| | `-- can-dom-events@1.1.1
| | `-- can-globals@1.0.1
| +-- can-dom-events@1.1.1
| | `-- can-globals@1.0.1 deduped
| +-- can-dom-mutate@1.0.3
| | `-- can-globals@1.0.1
| +-- can-globals@1.0.1
| +-- can-util@3.10.18
| | +-- can-event-dom-radiochange@1.0.5
| | | `-- can-globals@0.3.0 deduped
| | `-- can-globals@0.3.0 deduped
| +-- can-view-callbacks@4.0.1
| | `-- can-globals@1.0.1
| `-- can-view-model@4.0.1
| `-- can-globals@1.0.1
+-- can-compute@4.0.2
| `-- can-event-queue@1.0.1
| `-- can-dom-events@1.0.7
| `-- can-globals@0.3.0 deduped
+-- can-connect@2.0.4
| +-- can-ajax@1.1.4
| | `-- can-globals@0.3.0 deduped
| +-- can-types@1.1.5
| | `-- can-globals@0.3.0 deduped
| +-- can-util@3.11.3
| | `-- can-globals@0.3.0 deduped
| `-- can-view-import@4.0.2
| `-- can-globals@0.3.0 deduped
+-- can-route@4.1.1
| +-- can-dom-events@1.1.1
| | `-- can-globals@1.0.1
| `-- can-globals@0.3.0
+-- can-route-pushstate@4.0.2
| +-- can-dom-events@1.1.1
| | `-- can-globals@1.0.1
| `-- can-globals@0.3.0 deduped
+-- can-stache@4.1.2
| +-- can-globals@1.0.1
| `-- can-view-target@4.0.1
| `-- can-globals@1.0.1
+-- can-stache-bindings@4.0.5
| +-- can-dom-events@1.1.1
| | `-- can-globals@1.0.1 deduped
| +-- can-event-dom-radiochange@2.1.0
| | `-- can-globals@1.0.1 deduped
| +-- can-globals@1.0.1
| `-- can-types@1.1.6
| `-- can-globals@1.0.1 deduped
`-- shuttle-can-api@1.0.4
`-- can-util@3.11.3
`-- can-globals@0.3.0 deduped
+-- can-component@4.0.4
| +-- can-dom-events@1.1.1
| | `-- can-globals@1.0.0 deduped
| +-- can-dom-mutate@1.0.2
| | `-- can-globals@1.0.0 deduped
| +-- can-globals@1.0.0
| +-- can-stache@4.1.2
| | `-- can-globals@1.0.0 deduped
| +-- can-util@3.11.2
| | +-- can-event-dom-radiochange@1.0.5
| | | `-- can-globals@1.0.0 deduped
| | `-- can-globals@1.0.0 deduped
| +-- can-view-callbacks@4.0.0
| | `-- can-globals@1.0.0 deduped
| `-- can-view-model@4.0.0
| `-- can-globals@1.0.0 deduped
+-- can-connect@2.0.4
| +-- can-ajax@1.1.4
| | `-- can-globals@1.0.0 deduped
| +-- can-types@1.1.6
| | `-- can-globals@1.0.0 deduped
| `-- can-view-import@4.0.1
| `-- can-globals@1.0.0 deduped
+-- can-route@4.1.1
| `-- can-globals@1.0.0 deduped
+-- can-route-pushstate@4.0.2
| `-- can-globals@1.0.0 deduped
+-- can-stache@4.1.2
| +-- can-globals@1.0.0 deduped
| `-- can-view-target@4.0.0
| `-- can-globals@1.0.0 deduped
`-- can-stache-bindings@4.0.5
+-- can-event-dom-radiochange@2.1.0
| `-- can-globals@1.0.0 deduped
`-- can-globals@1.0.0 deduped
shuttle-can-api
that is up to no good... let me check
package-lock
package-lock
... will try Franks scalpel at some later stage. I published some of my package too so decided to just download everything again anyway.
package-lock=false