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

record-editor

v0.13.32

Published

Editor (used in inspirehep.net) for JSON documents with bibliographic metadata

Downloads

210

Readme

record-editor

Join the chat at https://gitter.im/inspirehep/record-editor Build Status Release Coverage Status

Editor (used in inspirehep.net) for JSON documents with bibliographic metadata

DEVELOPMENT

Tech

Development with inspire-next

On record-editor

# install the repo with npm
npm install

# link the module
npm link

# start build with watcher
npm start

On inspire-next

inspire-next has to be installed correctly before starting

  • add new line: ASSETS_DEBUG=True in $VIRTUAL_ENV/var/inspirehep-instance/inspirehep.cfg
  • run ./scripts/clean_assets where inspire-next source code is
  • run npm link record-editor at $VIRTUAL_ENV/var/inspirehep-instance/static
  • run honcho start where inspire-next source code is

On localhost:5000/editor

  • open editor (navigate to following)
    • /record/<type>/<recid> to edit a record
    • /record/<type>/search to search records to edit
    • /holdingpen/<workflow_id> to edit a workflow object
    • /multieditor to apply edits to multiple records
  • hard refresh the page whenever you want to see the changes

Development with inspire-next using docker

On inspire-next

inspire-next has to be installed correctly before starting

# Add the path to the editor in the volummes
vim services.yml

Add to the volumes list, the volume - "/path/to/your/editor/code:/usr/lib/node_modules/record-editor".

Remove all containers and start them up again:

docker-compose rm -f
docker-compose -f docker-compose.test.yml rm -f
docker-compose -f docker-compose.deps.yml rm -f
docker-composse up -d

Get a shell to the web container:

docker-compose exec web bash

Inside the web container, under /usr/lib/node_modules/record-editor

NOTE: you might want to completely clean up any existing installation on the repo, for that, you can run git clean -fdx inside the record-editor repo.

# install the repo with npm
npm install

Inside the web container, under /virtualenv/var/inspirehep-instance/static

# recreate assets
/code/scripts/clean_assets

# link the custom editor
npm link record-editor

Optional: inside the web container, under /usr/lib/node_modules/record-editor

# start build with watcher
npm start

If you don't do this, you'll have to manually install the editor to see any changes you make.

License

GNU GPLv2