Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@northeastern-web/global-elements

Package Overview
Dependencies
Maintainers
0
Versions
69
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@northeastern-web/global-elements

Northeastern global elements built with Tailwind CSS and Alpine.js.

  • 1.1.2
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
1.1K
increased by3.98%
Maintainers
0
Weekly downloads
 
Created
Source

Global Elements Package

Dependencies

  • NodeJS >= 12.x
  • NPM >= 8.x
  • kernl(ui) >= 2.x

Development

Builds

To build the project locally and prepare it for production use, run the following in the project's root directory:

  1. npm install
  2. npm run build

Preview (MacOS/Linux/WSL)

Note: To preview the Global Elements in your local development environment, ensure you have PHP configured on your machine:

  1. php -S localhost:8080

Github Workflow

Feature Branching

  1. Create a new Issue in the Global Elements Github repository. Provide as much context as needed for the issue
  2. Checkout develop branch then create a new feature branch off of develop with the issue number and title (e.g. git checkout develop && git checkout -b issue-1/remove-trailing-slash)
  3. Make fix in feature branch and create new commit with changes. Push changes to remote Github repository (e.g. git push origin issue-1/remove-trailing-slash)
  4. See Github merging and releasing workflow below

Merging and Releasing

  1. Create new Pull Request (PR) in the Github Repository to merge the feature branch into the develop branch
  2. Add a developer from Web Solutions team to review and approve the merge.
  3. Once merged, test the build on https://dev-global-packages.cdn.northeastern.edu/

Releases

This repository follows the major.minor.patch semantic versioning scheme.

To create a new release tag, run the following in the project's root directory: git tag -a v1.x.x -m "Release version x.x.x" where x.x.x is equal to the major.minor.patch semantic version.

Patches

For minor fixes or patches (no new features, fixes to existing features only), increment the ending patch version (e.g. v1.0.17 becomes v1.0.18).

Features

If there are large backwards-compatible (non-breaking) changes such as refactors or new features are being introduced, a new minor version release tag should be created (e.g. v1.1.0).

Large updates that are not backwards-compatible will require a major release (e.g. v1.0.18 becomes v2.0.0)

Usage

For up-to-date usage information, visit the kernl(ui) Global Elements documentation

FAQs

Package last updated on 10 Oct 2024

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc