![]() What I dont understand is why it does not work with CDN but works if I use react from a Webpack vendor chunk which will be a script that goes over app.js. On initial app load, the files do get copied to the dist folder so thats fine but I would expect that as I'm developing and updating these files, the app should also be reloading but it only seems to work for typescript files. Yes I am using server side rendering so the react scripts should load as the server returns the full page rendered. Here is some useful info: webpack command: webpack-dev-server -host 0.0.0.0 -config. It's still working, but each time use it, I need to do two things: (1) Enable LiveReload in SublimeText Using Ctrl + Shift + P Search and select 'LiveReload: Enable/disable plug-ins' Next select 'Enable: Simple Reload' (2) Enable LiveReload in the browser Click to LiveReload extension icon (it's turned on when the middle dot of the icon is black) I can do it fast but manually. Not that Ive tried webpack and the issue persists I am clueless. Looked for similar question here, but all I found was -watch, which did not help. When running command: npm run start:dev I would expect to see that every time I update my html files, then I should see the "incremental file change detected" message and the app reloads but nothing is happening after the initial app load. Short description of the problem: Livereload not working when using custom My custom is just a merge from the original adding new plugin What behavior are you ex. At first thought it is a problem with nodemon. ![]() I started a new project just to demonstrate what I'm seeing. And also add config> line183 (approximate) css compiler Append the above code on options object. I've tried in standard mode and mono-repo mode to no success. Go generated folder name: config>line166 (approximate) CSS compiler Append the code on options object. Even though I've followed exactly what this doc said: I can't seem to figure this out. I know that webpack-dev-server 4.0.0 recently came out a few weeks ago and has removed the need for a workaround of target: web when you have browserslist in your package.json. If you want to manually recompile the bundle, navigating to the /webpack-dev-server/invalidate route will invalidate the current compilation of the bundle and recompile it for you via webpack-dev-middleware. ![]() For some reason, the nest start -watch is not watching any non-typescript assets. Hi there, I have read through this thread and am not sure why the webpack config for my project does not seem to be working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |