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

teditor

v0.1.4

Published

npm install -g teditor & have a web IDE

Downloads

51

Readme

teditor

npm install teditor & have a web IDE

teditor is about to become a WebEditor that you will install with a single command.

npm install -g teditor && teditor

teditor presentation

$ teditor --help
usage: teditor --dir=. --host=127.0.0.1 --port=3000
        Then open your the shown port in the browser
options:
        --dir=.         the directory to edit int he ide, default is the current directory.
        --host=0.0.0.0  set this to 0.0.0.0 to access from anywhere, to a remove host, to accept only 
lets say from your home/office, default is localhost
        --port=3000     the port to bind, default is 3000

After a first version based on the code editor codemirror, the new version let you run vsCode in your browser. It can be installed on a remote server or on a micro computer such as the raspberry pi.

This is an experimental project, implemented just during a weekend and should not jet be installed public accessible.

Currently you can create, edit, rename, and move files and directories. This is already useful, when on the server you use utilities that watch the files and do automatic rebuilds and tests, such as webpack or nodemon. In future versions more features could be supported.

what work has been done:

checkout and run the vscode repo:

git clone https://github.com/microsoft/vscode.git
cd vscode
yarn install
yarn run web

These commands can run vscode in your browser, however a virtual in memory filesystem is used. I used tstaticstoringproxy to save to all the files the browser would load into a directory. so I can do my adjustments in them and only have the files in this package, that are needed to run vscode, without the need for additional compilations.

Experimenting with this code and configuration, I found to change the configuration to an http filesystem. however most of its functions have not been implemented. So I edited the public\static\out\vs\workbench\services\extensions\browser\webWorkerFileSystemProvider.js to do use the browsers fetch to interact with a server.

The server is currently completely implemented using express and lives completely in a single file, the index.js.

Plan

When I, you or we want to go forward with this project, we can cleanup the code. add features to use vscode debug run functionalities to send commands to the server that could run, based on the users definitions.

We could see if we can support more features.

Currently it is a manual process, of checking out the latest version of vscode and compile it to be used in teditor. We can try to automate it.

History

  • added experimental support for terminal. I don't want to use node-pty, as it is a native module and requires c-compiling, that is a pain in the ass. So simply use a child process here. Still need some more improvements.