- Remove cache when window close
- The information on the package can now be displayed as soon as received
- Package version refresh is now asynchronous and will be done after a quick display
- Added Option to specify cache refresh frequency
- Added command to clean cache
- Fixed linter reporting issue #8 (thanks to @jsg2021)
- Added option to specify NPM client
- Reduced npmrc file read to optimize first package.json file opening duration
- Feature #3, the scope specific registries are now supported in
.npmrc
- Fix issue #2 relative to non semver version checking
- Add the feature to install or update a dependency package
- Fix unfound package message to Linter2 format
- Disable the installed package version check per default
- Fix node-fetch version
- Fix latest stable version in warning message
- The solutions proposed by the linter now includes an NPM install with the page update
- The Lodash dependency has been removed
- Generate the version prefix based on current version
- Support for Linter Message v2
- Add title to the suggestions
- Fixed solution range issue
- Fix code according to ESlinter issue
- Fix hyperlink underline issue
- Add a configuration for the NPM package information website
- Activate the package on JSON grammar hook
- Hyperlink can you send you to the npmjs website by clicking on the package name
- Fix issue on auto complete feature
- Catch error on new invalid dependency typing check
- Add available options list in the documentation
- Reduce the number of function requiring the Atom specific object
- Fix info message
- Fix issue in info display calculation
- Added caret option in the linter fix suggestion
- Changed information message to display info only on not enough restricted package version
- Restrain the package version suggestions to the dependencies only
- Fix custom registry handling
- Added auto-complete feature screenshot in readme
- Fix auto-completion to be trigger on value only
- Extract linter code from the actual worker
- Implement auto-completion for module version
- Fix the way to determine if the package is not found
- Based the
.npmrc
file on project base path - Fix registry decoding
- Allow the user to configure the prerelease level to check
- Optimization of the execution speed
- Stop reporting if the
package.json
file is invalid - Handle not found package exception
- Moved stable version information in Trace message
- Increased the reactivity by storing the list of available versions
- Reduce added loading time to Atom (from 1000ms+ to >90ms)
- Remove current version from Linter message
- Implementation of the support for scoped package
- Fix for the invalid package version check
- Implementation of NPM outdated command based on Atom Linter
- Creation of fix suggestion