search

caiobiodere / cordova-template-framework7-vue-webpack

Framework7 - Vue - Webpack Cordova Template with Webpack Dev Server and Hot Module Replacement
Apache License 2.0
620 stars 154 forks source link

Webpack appears to be stuck in a re-compile loop #88

Closed theMangledBadger closed 6 years ago

theMangledBadger commented 6 years ago

Hey,

Firstly, thanks for the source code, I've found it really useful.

When running the command 'cordova run browser -- --live-reload', the compiler appears to constantly recompile the project, outputting this message in terminal:

Use of cordova.raw.* methods is deprecated and cordova.raw will be removed in a future release. Please migrate to using the top-level cordova.* methods instead. Update happened. Skipping... [ 'www\\platform_cordova_files\\browser\\config.xml', 'www\\platform_cordova_files\\browser\\manifest.json', 'www\\platform_cordova_files\\browser\\index.html' ] webpack: Compiling... Use of cordova.raw.* methods is deprecated and cordova.raw will be removed in a future release. Please migrate to using the top-level cordova.* methods instead. Update happened. Skipping... [ 'www\\platform_cordova_files\\browser\\config.xml', 'www\\platform_cordova_files\\browser\\manifest.json', 'www\\platform_cordova_files\\browser\\index.html' ]

And in the browser I just see:

XHR finished loading: GET "http://127.0.0.1:8081/6590ffb6e65eb48d449b.hot-update.json". (anonymous) @ 46f4140409574b676af8.main.js:32 hotDownloadManifest @ 46f4140409574b676af8.main.js:24 hotCheck @ 46f4140409574b676af8.main.js:226 check @ dev-server.js:13 (anonymous) @ dev-server.js:47 EventEmitter.emit @ events.js:81 reloadApp @ client:225 ok @ client:139 onmessage @ socket.js:41 EventTarget.dispatchEvent @ sockjs.js:170 (anonymous) @ sockjs.js:883 SockJS._transportMessage @ sockjs.js:881 EventEmitter.emit @ sockjs.js:86 WebSocketTransport.ws.onmessage @ sockjs.js:2957 [WDS] App updated. Recompiling... [WDS] App hot update... [HMR] Checking for updates on the server... [WDS] App updated. Recompiling...

Any ideas as to why this behavior is happening?

theMangledBadger commented 6 years ago

Actually, I appear to have solved it.

When creating components, it's important to wrap them in a tag otherwise the DOM hasn't a clue where to look for the item.