Search Results for "packages"

This plugin adds Go language support for Vim, with the following main features. Look up documentation with :GoDoc or :GoDocBrowser, easily import packages via :GoImport, remove them via :GoDrop. Precise type-safe renaming of identifiers with :GoRename. See which code is covered by tests with :GoCoverage. Add or remove tags on struct fields with :GoAddTags and :GoRemoveTags. Call golangci-lint with :GoMetaLinter to invoke all possible linters (golint, vet, errcheck, deadcode, etc.) and put the result in the quickfix or location list. ...

A Serverless Framework plugin to build your lambda functions with Webpack. When enabled in your service configuration, functions are packaged and compiled individually, resulting in smaller Lambda packages that contain only the code and dependencies needed to run the function. This allows the plugin to fully utilize WebPack's Tree-Shaking optimization. Configuration possibilities range from zero-config to fully customizable. Support of serverless package, serverless deploy and serverless deploy function. Support of serverless invoke local and serverless invoke local --watch. ...

...Communication with receiver devices is handled by a companion application (bridge). Install the Firefox extension (from within Firefox) and bridge application via the installer packages. These are two separate downloads that can be found on the website or in the GitHub releases section. The bridge application is currently supported on Windows, macOS and Linux. Clicking on the toolbar button or Cast... menu item in the page context menu will open a popup that shows a list of receiver devices will allow you to start casting the currently detected app2 or media. ...

This is a composer 1.x plugin that downloads packages in parallel to speed up the installation process. This plugin is for Composer1; Composer2 is very fast on its own. Recognize composer's options. You don't need to set any special configuration. To avoid Composer asking for authentication it is recommended to follow the procedure on composer's authentication. For github.com you could also use an auth.json file with an oauth access token placed on the the same level as your composer.json file.