Closed viveksachdeva closed 6 years ago
Hi, yes, you're right, the configuration doesn't support auto-reloading of the browser (known as Browser Sync), and it also doesn't automatically push changes into AEM (AEM Sync). It only watches file changes to run the Webpack bundling process. Browser Sync and AEM Sync don't work by default. There are various ways to implement it, and I found that different people and projects have different preferences, so I didn't want to make it part of the project by default.
Here are a few options you can check out:
Thanks for superquick @kevinweber. If this project it not pushing to AEM and no browser sync.. and it seems that I have to statically include JS/CSS in the HTML, why is this called aem-weback-example.. Other than the folder structure, what other thing is AEM like..?
Valid question. Let's discuss this. We just published a blog post describing some concepts we thought about when setting up Webpack in AEM. The post answers a few questions that are implemented in AEM Webpack Example, namely:
Read the post: http://www.infielddigital.com/blog/webpack-in-aem/
What other ways do you imagine for integrating Webpack into AEM?
One thing to keep in mind is how AEM deals with some of the "reserved words" so using webpack to make bundles (that might use require and default syntax) might cause issues. JS Bundling in general using require/imports mess up the js.txt usage. How are you guys handling that?
@Aourin I'm not sure what you mean by that. We haven't had issues with clientlibs related to Webpack. Can you give an example and explain how you are handling this?
I followed the instructions mentioned in the README. Still not able to get it to work. From the video, it seems that we are checking page from file system rather than AEM instance. Is that right?
My expectation was that any page/component running on AEM would auto-reload when I make change to the html file like it is happening in the video