oasp / generator-oasp Goto Github PK

npm installation doesn't include oasp-base-generator.js file which leads to errors when using sub-generators. Placing the file manually fixes the problem.

In spite of already installed yeoman, I had a problem by executing
npm install -g generator-oasp

UNMET PEER DEPENDENCY yo@>=1.0.0

I needed to explicitly add "yo" here in order to install the generator:
sudo npm install -g yo generator-oasp

Please Use karma direct instead of deprecated gulp-karma.

https://github.com/karma-runner/gulp-karma

Hi,

I have faced a problem concerning browser sync and usage of not cached html templates (by cached I refer to the ones converted to .js file with appropriate initialization of $templateCache). When running gulp serve all html files that are asynchronously loaded by angular js are extended by browser sync with a custom script tag. Unfortunately it can lead to some problems. In my case the problem was revealed when adding ui-router to the project. In final step of view switching it runs:

$element.html(locals.$template ? locals.$template : initial);

In current project configuration jQuery is plugged in and as a result its implementation of .html is being called. jQuery is so smart that it copies all scripts and then run global eval on them:

if ( hasScripts ) {
    doc = scripts[ scripts.length - 1 ].ownerDocument;
    // Reenable scripts
    jQuery.map( scripts, restoreScript );
   // Evaluate executable scripts on first document insertion
   for ( i = 0; i < hasScripts; i++ ) {
       node = scripts[ i ];
       if ( rscriptType.test( node.type || "" ) && !data_priv.access( node, "globalEval" ) && jQuery.contains( doc, node ) ) {
            if ( node.src ) {
     ...
           } else {
                 jQuery.globalEval( node.textContent.replace( rcleanScript, "" ) );
           }
      }
   }
}

For us it means that script attached by browser sync will run, what causes the whole view to be cleared (I did not check if the same occurs in case of using jqLite).

If we want to provide a flexible and stable development environment it should not cause such exceptions/problems.

Imho html files should not be watched anyway, because if developer has already entered the view, then the template was loaded and cached in $templateCache. Browser sync is able to inform the browser to refresh resources, but not to inform angular to refresh its cache. In case of generated cached templates everything seems to be fine - run method will be executed on the reloaded module so entries in $templateCache will be replaced.

Cheers,
Bartek