-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IMPROVEMENT] Fix for Issue #30 #31
Open
itnok
wants to merge
15
commits into
sebdeckers:master
Choose a base branch
from
itnok:patch-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…orrectly calculated) The `fs` library is already included and it looks like it works better than `grunt.file`. With files bigger than few kilobytes the hash is calculated in the right way. It looks like `grunt.file.read` either does not read the file correctly or not in full. This change solves Issue sebdeckers#30
Oops! Sorry... :-)
Signed-off-by: Simone Conti <[email protected]>
Default to UTF-8 Signed-off-by: Simone Conti <[email protected]>
Signed-off-by: Simone Conti <[email protected]>
- Updating to v0.1.1 This will permit npm to better track changes and let user download the latest version. Signed-off-by: Simone Conti <[email protected]>
Perhaps even not release candidate versions... Signed-off-by: Simone Conti <[email protected]>
Let's see if Travis CI like it a little bit more this way... Signed-off-by: Simone Conti <[email protected]>
npm version 2.0.0 is the first where the "caret bug" was removed: ^0.x.y is now functionally the same as ~0.x.y Signed-off-by: Simone Conti <[email protected]>
Signed-off-by: Simone Conti <[email protected]>
Update npm before script starts to avoid troubles with "^" in packages requirements. npm can be newer that node... and it actually should. Signed-off-by: Simone Conti <[email protected]>
Signed-off-by: Simone Conti <[email protected]>
It also looks like grunt-cli installation is mandatory Signed-off-by: Simone Conti <[email protected]>
We are dropping tests on node < 0.10.0 We are alos using updated dependencies We should be modern, right?! Signed-off-by: Simone Conti <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem/BUG => hash for big files was not correctly calculated
The
fs
library is already included and it looks like it works better thangrunt.file
.With files bigger than few kilobytes the hash is now calculated in the right way.
It looks like
grunt.file.read
either does not read the file correctly or not in full.This change solves Issue #30