Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
@goodshuffle/gspro-wc
Advanced tools
Readme
Use these webcomponents to make your Goodshuffle inventory available on a website.
You will need a recent installation of an LTS version of Node.js (12.18.3).
On MacOS X, you can install this using brew
.
brew install node
If you anticipate working on multiple projects that use Node.js it may be helpful to install nodenv.
Anyone familiar with sdkman, rbenv, or pyenv should feel right at home. Other solutions for managing multiple versions of Node.js can be used, but nodenv
is recommended.
After cloning the project, run the following command to install project dependencies.
npm install
Run a local server.
npm run start
After running this command, your system's default browser should be opened and the content of ./src/index.html
displayed. This page is used to do some live exerimentation during development. If a valid data source is not available, you will see the message "Categories temporarily unavailable."
By default, the project will reference a locally running version of an HTTP service that provides wishlist data. Typically, that project will be configured to reference remote deployments services (RabbitMQ, Elasticsearch, and PostgreSQL). Please see https://github.com/goodshuffle/gspro-data-api/blob/master/README.md for more info.
You may also change ./src/index.html
to reference a test, demo, or even production URL for data if you do not wish to configure the wishlist HTTP services. Look for the following tag, and set the content like such. Just be aware that if you're doing local development that you should be referencing an http (not https) URL.
<meta name="gspro-config"
content="https://test.goodshuffle.com/vendor/:public-website-key:" />
Before releasing a new version of the library, you should stop your local development server. This should prevent potential development build artifacts from appearing in production builds.
This project uses Semantic Versioning 2.0.0
Update the release version in:
Note: once the release is finalized, you will need to update several other places with the new version:
Next, run the build.
npm run build
Finally, you can publish the new version to NPM. Please be aware that you may need to run npm login
if you haven't already.
npm publish
You will need an NPM account and be authorized to publish projects to the @goodshuffle organization. Two factor authentication is required to publish changes to the project.
We suggest that wishlist customers use UNPKG to retrieve the library. This is a reliable and high-performance CDN that makes it trivial to include the library on websites. At the time of writing, UNPKG provided approximately 88 billion downloads in the previous month. Please refer to the documentation to understand how ambiguous versions (e.g. 2.0) are resolved to the latest matching version.
FAQs
The Goodshuffle web components library.
The npm package @goodshuffle/gspro-wc receives a total of 15,012 weekly downloads. As such, @goodshuffle/gspro-wc popularity was classified as popular.
We found that @goodshuffle/gspro-wc demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.