Recently, I incorporated angular-seed into a coding challenge for a job interview. Feedback I received mentioned that keeping bower_components inside the app folder was not ideal.
Question 1: Is it truly considered bad practice to have bower_components within the app folder?
Following the feedback, I decided to relocate bower_components to the same level as the app folder. This created issues with references in index.html as they were expecting bower_components to be within the app folder.
Question 2: How can I reference bower_components outside the app folder? Would there need to be a build step involved to copy the app to a ./public folder and then copy bower_compnents into ./public/app before starting the server and configuring it to serve static files from ./public/app?
I attempted to modify the "prestart" command to achieve this, but it didn't seem to sit right with me. Additionally, making changes in the app folder required restarting the server each time to see these changes reflected in the browser.
What is the recommended practice in this situation? I know that the yeoman generator places bower_components outside the project root, using gulp/grunt tasks to adjust references. However, I prefer angular-seed for its minimalistic approach and would like to solely rely on npm for build tasks.