This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| v0.10.1 | |
| hotfix | |
| FIXES IE11 exception in broken array-copy wrapper (error message: "Function.prototype.call: 'this' is not a Function object) | |
| We attempted to use the recommended technique where available to do shallow copy operations on Array-like types (assuming Array.from where available would be better). All recent browsers are implementing the Array.from method, why we noticed this bug too late. The way we were calling Array.prototype.slice on IE11 was ineffective: our compatiblity-wrapper function was crafted in the wrong manner - as we have learned in a painful way. | |
| See #1786 | |
| Our main take-away here is improving our CI acceptance testing in browser VMs, so we can have confident automated testing on IE11 as well, and notice such issues before we merge them :shipit: | |
| Also, we have now actually acknowledged that slice is usually more performant, which might be because of Array.from supporting a more wide range of parameters: https://jsperf.com/array-from-vs-array-prototype-slice |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| import App from './App.svelte'; | |
| const app = new App({ | |
| target: document.body, | |
| props: { | |
| name: 'world' | |
| } | |
| }); | |
| export default app; |
Отладка SmartTV больная тема для большинства разработчиков. Мысли о том, что придется делать все в слепую отталкивают разработчиков, что негативно влияет на отрасль SmartTV и Web в целом. Я рассказажу, что не все так плохо и инструменты существуют. А те, которых нет не сложно запилить самому.
While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.
Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.
lib/is intended for code that can run as-issrc/is intended for code that needs to be manipulated before it can be used