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

webgme-icore

v2.0.2

Published

Integrated code-editor for interacting with webgme models from the UI.

Downloads

23

Readme

ICore

Code-editor for interacting with models uses the same APIs available from a plugin (the provided context is the main function of a plugin). Note that this visualizer uses eval to evaluate the code and is recommended to only be used at dev-deployments or at least not at deployments where security is a major concern.

View instruction video here!

ICore

The editor provides code completion for the major webgme APIs and dynamically generates the current META. To bring up the suggestions hit [Ctrl + Space] (links to the source code documentation are available). For better user-experience do not rename the variables providing the APIs.

Importing into other repository

webgme import viz ICore webgme-icore

Once imported and server is restarted, register the visualizer at the nodes where it should be used. If the 'scriptCode' attribute (configurable) isn't defined the model will have meta-violations after saving the code.

Python specifics

In general we do not recommend to use the python mode unless the users on the deployment are trustworthy and/or the deployment doesn't deal with sensitive data.

In order to enable python execution you need to import the PyCoreExecutor plugin.

webgme import plugin PyCoreExecutor webgme-icore

and config.plugin.allowServerExecution = true; must be added in the config.

Since the python mode will run user defined code on the back-end we strongly recommend using webgme-docker-worker-manager. together with a version of ./DockerfilePyCoreExecutor. (For an example of the configuration parameters needed for this to work check out ./config/config.docker.js and ./docker-compose.yml.)

Finally import the router that serves the python source code documentation:

webgme import router BindingsDocs webgme-bindings

Developers

Docker compose

If running on unix-like system this repo can be launched using docker-compose. See ./docker-compose.yml for useful commands and details.

docker-compose up -d

Visit localhost:8888 from your browser.

Notes:

  • The database-files will be persisted inside the container and the blob-files inside the webgme-server container.
  • The webgme-server launches "docker-workers" on the host machine.

Running at host

Make sure the dependencies for webgme are installed.

  1. Clone this repository
  2. npm install - installs all dependencies
  3. npm install webgme - installs webgme (it's a peer-dependency).
  4. Launch a local mongodb instance (if not local edit the webgme config).
  5. npm start
  6. Visit localhost:8888 from a browser.

Publish new release at npm

npm version 1.0.0 -m "Release %s"
git push origin master
git checkout v1.0.0
git push origin v1.0.0
npm publish ./