I think solution is not hard, I’ve just something obvious. I have a simple project on TS. Without any modules, just TS for compilation. TS-files compiling into js-files at dist folder, and than they all connect into app.js(ts), which connect at index.html(structure of project you can see on photo). When files compilated, there aren’t any errors, but browser can’t find
Tag: compilation
In V8, what is lazy deoptimization, and how does it happen?
According to V8 source code and turbofan materials, there is a type of deoptimization called lazy deoptimization which is described as follows(v8/src/common/globals.h): Lazy: the code has been marked as dependent on some assumption which is checked elsewhere and can trigger deoptimization the next time the code is executed. However, when observing the execution of ‘v8/test/mjsunit/compiler/deopt-lazy-shape-mutation.js’ with d8, I found that
Webpack successfully builds, but JavaScript doesn’t execute runtime
I have migrated Webpack v4 to v5, made changes relative to documentation and deprecation messages from CLI, and got successful build, though during the application testing I noticed that JavaScript doesn’t run and there are no errors. I am getting plain html rendered by SSR. Have no clue why it doesn’t work, because it’s silent, maybe misconfiguration issue. Here is
Vue 3 recommended TypeScript TSConfig compilerOptions TARGET setting?
This question has puzzled me at several points when using Vue 2 and Vue CLI, and now again with starting a fresh Vue 3.0 beta project. Even with the currently newest Vue CLI version 4.3.1, when choosing TypeScript option, the boilerplate code you are given has compilerOptions target set as esnext in tsconfig.json. While Vue 2 TypeScript Guide is instructing: