greenkeeper[bot] on core-js-3.4.8
chore(package): update core-js … (compare)
cherifGsoul on update-infrastructure-page
Update infrastructure page with… (compare)
greenkeeper[bot] on @feathersjs
chore(package): update @feather… (compare)
greenkeeper[bot] on @feathersjs
chore(package): update @feather… (compare)
greenkeeper[bot] on core-js-3.4.7
chore(package): update core-js … (compare)
greenkeeper[bot] on core-js-3.4.6
chore(package): update core-js … (compare)
peerDependencies
for host app. So its like app where you use custom-button
decides which version it will use and injects only one version of any stylesheet. But this adds some field to make mistakes, if you publish something incorrectly.
generally speaking, it will be as simple to add as finding these logs:
https://github.com/canjs/can-fixture/blob/master/core.js#L197
if(fixture._log) { ... }
Has anyone seen an error like this before?
Uncaught DOMException: Failed to execute 'pushState' on 'History': A history state object with URL 'http:/#admin/posts' cannot be created in a document with origin 'http://localhost:8080' and URL 'http://localhost:8080/#admin/posts'.
can-route-pushstate
. I'm trying to figure out why it's happening, but if anyone knows where to look and can save me some time, that would be great. The router works fine in this application in development mode, but throws that error when using steal.production.js.
route
is a semi-reserved word
can-route-pushstate
and running into the same issue, I’d be curious about what’s going on in these two places: 1) https://github.com/canjs/can-route-pushstate/blob/24dabe72b79acfcd30e516fc78599794d4f205b0/can-route-pushstate.js#L207 and 2) https://github.com/canjs/can-route-pushstate/blob/24dabe72b79acfcd30e516fc78599794d4f205b0/can-route-pushstate.js#L234
@/all We’re going to have a live stream right now about the next survey’s proposals:
https://forums.donejs.com/t/donejs-community-survey-november-2018/998
Live stream:
can-fixture
, but there is in a lot of other canjs code
Hi guys, what "crossed" items means in this issue:
https://github.com/canjs/canjs/issues/4115#issuecomment-434448401
can
released with IE11 support. You might want to watch this PR too. 😊 canjs/canjs#4600
property
changes?
4.X
, I'd suggest using connectedCallback()
instead of the events
object