Conversation
Isn't it a pity to remove perfectly working code (as far as I used it) while it's replacements have still issues producing a production build? Wouldn't it be sufficient for the time being to add a notice that this code is no longer maintained? |
@trendzetter It prevents the framework from getting bloated. Templatecache is not in grunt, it's only in gulp. We've been adding things to gulp lately in favor or grunt. Grunt is still in the 0.4 releases. |
Agree with @trendzetter; I would vote for continued grunt support. I don't see where gulp covers the Lines 218 to 226 in e140880
|
There's a bit more work to do to get Gulp in line with the tasks that exist in our Grunt implementation. This PR is a great starting point to get that conversation going, as Cody said. Look at all the dependencies we get to remove, when we get rid of Grunt. The more dependencies this framework has, the more likely we'll run into issues with environmental compatibilities. Ive run into quite a bit of issues with Grunt. Not really at all with Gulp. Again, like Cody said, the 0.4 releases will have Grunt. Even if someone were to install, or upgrade to 0.5.x, they would be able to add Grunt very easily. It would be a matter of a few copy & pastes. @codydaig I'll help out with getting Gulp ready for this to be merged. I know the tasks pretty well, between the two. |
@codydaig I am very much in favor of lean and mean. I also value continuity and stability as a user of the framework. It appeared to me that when tracking the upstream I could run into issues with producing occasional production builds. |
@trendzetter what issues have you had with Gulp? |
I am just referring to #1160 |
@trendzetter that is something that doesn't even exist in our Grunt setup, so that is not an issue really. Please try Gulp and let us know what else needs to be added to allow us to switch over from Grunt to Gulp. |
I not sure what you mean by "that doesn't even exist in our Grunt setup". |
@trendzetter nothing in Grunt creates a template cache for Angular in the same way that Gulp does. What you are referring to is minification, which both build tools already do. |
@ilanbiala Sorry for my ignorance. I just tried the minification build and they both run the same at first sight although the grunt dist files are 1kb smaller. |
Thoughts on using: https://www.npmjs.com/package/gulp-strip-debug Would be nice to have some debug statements in the code base. Like on controller instatiation do console.log('ArticlesController::Init', vm); Then let gulp strip them on production/test build. Obviously we wouldn't allow all console.logs in PR's, but having strategic ones would save a bunch of time IMO Thoughts? |
@trainerbill I don't think we have that in Grunt, so that should be in a different issue. This issue is just about getting everything in Grunt into Gulp so we can strip Grunt out. |
@codydaig The following tasks can be added to the list
Not sure if we need these. Does anyone have any insight? |
thanks @mleanos |
@mleanos where are we using ngAnnotate? |
@@ -16,7 +16,7 @@ | |||
}, | |||
"scripts": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Scripts were already taken care of: 5a91d7d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I'm gonna close this PR in favor of a new one. Some things have changed.
I'm fine with removing Grunt officially. I had reservations on supporting users that rely on Grunt already. However, as someone pointed out earlier, anyone can look back at previous versions of the framework to see how to integrate Grunt. |
I think we can merge this in, after the conflicts are resolved (re-base). Everything but the |
@codydaig Would you like to wrap this one up? It looks like this is the last key issue before we're ready to release 0.5.0. |
@mleanos Rebased. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
9 similar comments
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Coverage remained the same at 73.224% when pulling 204ab55d868fdd489af27b79ade605c72f6a4a32 on codydaig:removeGrunt into 287f81c on meanjs:master. |
Despite the one build chain failing, the other passes. It also passes when it runs on my fork of mean. @mleanos I believe this is ready to be merged in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Look at all those libraries we're removing 👍
Yay, finally! :) |
@codydaig qq -Is there a reason why Grunt and Grunt-Cli are left out in the dependencies? |
This PR serves as the PR to remove grunt, but also as the discussion of what needs to be accomplished before this can get merged in. Is there any functionality still in grunt that is not in gulp? I will add todo items left in comments to this description.
Tasks still to be added to Gulp:
grunt coverage
feat(tests): Add client and server test coverage to Gulp #1466copy:localConfig
feat(gulp): Add the copy:localConfig task to Gulp #1191mkdir:upload
ngAnnotate
mongoose
(unnecessary)node-inspector