you can return from getTemplate() => stache('<templateString')
that works at last for me
but you should maybe consider the following extra
getTemplate should get called with scope
and then return also stache(templateString)(scope)
if sending non-data messages to the server, would one still use
can-connect or is that overkill? If so, what is recommended? can-ajax? something else? thanks.
@frank-dspeed yes, that is how I do it now. Many thanks to @roemhildtg !!
@dbleier We use a
can-construct with some functions that call can-ajax or $.ajax
@jeroencornelissen ok, I was thinking something along those lines, thanks
lol
Messages are DATA?
for example command requests for the server to do something, where I don't really need a response back
Remote Transfer Protocol
don't sends a response back
TCP/IP Always does
anyone know why I'd be getting this?
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
the odd thing is I have another project and it works fine there
same versions of everything although there is going to be something different I'm sure
the
can-globals in the working project has the /is-web-worker/ folder yet the other does not
npm ls can-globals
quite a tree:
+-- 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
that's the one that ends up in 0.3.0
here's the one going to v1.0.0:
+-- 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
ah, seems to be my
shuttle-can-api that is up to no good... let me check
I have a
package-lock
you could try deleting it, clearing out your node_modules, and re-installing
could just be a locked version not allowing it to update
npm install can-globals@1.0.0 --save
after that npm ls if your on current npm version you should get all deduped to 1.0.0
and after that if you do npm remove can-globals
all should get 1.0.0
@frank-dspeed that'll probably work but then I'd be "referencing" it directly, right?
so add and then remove
if you have nested versions already, that won't fix it right?
i use that flow often with canjs apps
when such dependency stuff happens
also works good for upgrades
npm team did fix a lot
oh and i want to share a secund good method search and replace in the package-lock.json and npm install should also fix
it can also be a cached resolved version @phillipskevin
npm stores now like yarn its own data in .npmrc
@phillipskevin I did go with the big hammer and deleted the
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.
use npm outdates and then npm update can-outdated can-xxx
and also all sub dependencys
a lock file now gets linked to resolve info in your npmrc directory
been busy with .net core refactoring so need to get back into the canjs swing of things
if lock exist cache get touched
if you general want no lock file
that saves you the trouble with creating deleting if you don't use that flow anyway
will keep it in mind; until I forget, that is
i was to far in future the lock parameter for package.json as boolean is not existing at present
will come in some month :)
at present you would create a .npmrc file
in your project with the following content
package-lock=false
or you can set it global
npm config set package-lock false
in my dev environment i use that global setting
and the ci don't has that setting so it publishes with lock
in general thats the best flow overall
thanks i am sorry that i did not found time to finish my started guides about all that
but i am planning massiv guide releases in 2018 about development workflows i will keep you informed
i have invented really slick dev environments
with as much release automation as possible
there is just a ton of stuff to learn nowadays so I'm quite glad I'm not getting into development in this day-and-age!
a Mix of Mono and Multi Repo
:D
including automated flows
so you have both a single repo to track them all and still individual packages
using git submodules as main tech
worked with Linus on that directly
the creator of git to define standarts for javascript development with git
because the industrie needs standarts to enforce security
and this package workflows have a bunch of complex security issues as npm packages can get hacked and all that
thats also why the github security risk implamentation now exists for javascript packages
I've received some security warnings from github about packages I use...
so it works :)
in future we will also block install of that
via npm integration ;)
we also have runkit implamented look at that slick stuff
a full canjs playground
but it gets even better this runs it all server side
:D so you could for example run your server side packages there
like donejs apps
same like jsbin for frontend for the nodejs backend
with all npm packages pre installed!
and free api
have to give it a spin some time
you can now test every package online
without installation
the next step is now to combine it with some frontend rendering then we can do frontend backend examples in the same environment
all without install
i will try to release this year a Plugin for vscode and atom to online edit and export that
for frontend and backend this will allow to develop modules online without install of dependencys
will save a lot of time