- Initial release
- Documenation updated to include WARNING
- Roadmap added to docs
- Better commit message during a Bump command
- Removed skipping NPM install message during uninstall
- Init command adds
.git
to repository field inelm-package.json
- Init will NOT run if
elm-package.json
already exists
- Forgot the update instructions in the readme
- Configuration command to run in safe mode to only install Official Elm Packages (local and global configurations)
- Init command prompts to create minimal
package.json
- Changed default license for Init command from
BSD
toBSD-3-Clause
- Github sources were being added to
dependency-sources
- Fixed install/update instructions in the readme
- Config command now supports
--docs
- New command
docs
will generate Elm docs - If configured, the
bump
command will generate Elm docs intoelm-docs
- Added
--link
to theuninstall
command since uninstall does a reinstall and the reinstall will use this flag
version
command was reading from the current directory not the Grove directory- Added missing documentation for 1.0.6 features
- Changed
file:\\
togit+file:\\
for npm dependencies that are locally linked so npm will install from the directory instead of just linking to it - Don't add semver to linked npm dependencies
- Fixed bug (issue #8) when installing via SSH from github.com
- Enforces Semantic Versioning - Bump will determine proper version based on changes to public interface
- Normal, Rebased and Legacy release support
documentation.json
is now generated in current directory for tools, e.g. elmjitsugrove-config.json
is now.grove-config.json
(automatically renamed when you run Grove)
- 3rd party
package.json
files are no longer held to the same standards as the ones for the current project's- Validation errors are just Warnings
- Validation is only done if 3rd party package has
nativeModules
- Elm packages are only included in your
package.json
if the package hasnativeModules
- Init command's validation of repo names didn't allow for numbers
grove init
followed directly by agrove install <some-package>
would NOT updatepackage.json
with dependencies if<some-package>
had dependencies
- Fixed issue #12 where the
package-lock.json
file wasn't being updated duringbump
- Fixed bug where
package.json
was being read from the master branch instead the checked out version. This was only an issue when a newer version of a library existed that has Native code - Updated to latest version of
panosoft/elm-docs
which fixed bug with Table of Contents generation and duplicate entries
- Use newer version of
elm-docs
which uses the source code signatures instead ofdocumentation.json
signatures which are not formatted
- Use newer version of
elm-docs
which fixes elm-docs Issue #2