hangar-alpha
Advanced tools
Share frontend assets between different web repositories
The workflow for development will be usually this:
grunt dev in one tab to see the styleguide html view working, which is open by default.grunt test in another tab to run the tests. This uses karma underneath.For more details, take a look to the Grunfile to see all tasks available.
In order to release a new version of Hangar, from master branch run:
npm run release
This will make a new build, publish the new version to github pages and then launch the interactive UI that guides you through publishing a new version to npm and unpkg:
As we already published hangar to npm, unpkg.com is the best choice, and the good thing is, we don't need to do anything to version the assets:
Use @latest as latest version.
FAQs
Share frontend assets between different web repositories
We found that hangar-alpha demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 11 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Five malicious NuGet packages impersonate Chinese .NET libraries to deploy a stealer targeting browser credentials, crypto wallets, SSH keys, and local files.
Security News
pnpm 11 turns on a 1-day Minimum Release Age and blocks exotic subdeps by default, adding safeguards against fast-moving supply chain attacks.
Security News
The remediated findings include organization permission bugs, stale project access after transfers, OIDC replay edge cases, audit logging gaps, and an IDOR in API token deletion.