npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@cognite/3d-web-parser

v0.13.7

Published

Parser for Cognite 3D viewer

Downloads

21

Readme

JavaScript parser for 3D web files

Build Status codecov

This module parses 3D data from Cognite Data Platform used in the 3D viewer.

Using typescript

This module is written in native typescript, so no extra types need to be defined.

License

Apache 2.0

Development

Run all tests:

$ yarn
$ yarn test

We use jest to run tests, see their documentation for more information.

Update protobuf schema

  • Run yarn run pbjs -t json -o src/proto/web_scene.json {path to web_scene.proto}

Releasing

How to release a new patch version

New patch releases are usually based on the release branch for the given minor version.

  1. Checkout the release branch for the previous minor version, named releases/x.y.
    git checkout release/x.y
  2. Create a new branch for your changes
    git checkout -b yourusername/release/x.y.z
  3. Cherry-pick your changes from the master branch or add new commits.
  4. Update package.json with the correct version in the header.
  5. Push your branch
    git push
  6. Create a new pull requests from yourusername/release/x.y.z into the release/x.y branch.
  7. Wait for review and merge. After merge, switch to branch release/x.y and pull changes.
  8. Tag last commit with version, i.e. "vX.Y.Z".
  9. Push tag
    git push --tags
  10. A new version will be published when the tag is pushed.

How to release a new minor or major version

New minor or major releases are usually based directly on the current version in master.

  1. Checkout the master branch.
    git checkout master
  2. Create a release branch.
    git checkout -b release/x.y
  3. Push the branch.
    git push
  4. Create a new branch for your changes:
    git checkout -b yourusername/release/x.y
  5. Create a version commit by running.
    $ npm version [minor/major]
    # example: $ npm version minor
  6. Push branch and push tags (git push --tags)
  7. Create a new pull requests from yourusername/release/x.y.z into the release/x.y branch.
  8. A new version will be published when the PR is merged