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

vscode-test-get-content

v2.2.0

Published

A set of helper functions for getting content of the Visual Studio Code instance.

Downloads

33

Readme

vscode-test-get-content Build Status

Provides a set of helper functions for getting content of the Visual Studio Code instance.

This helper is designed to be used in VSCode tests / extensions only.

Usage

Simply getting the editor's content:

const vscode = vscode = require( 'vscode' ),
	getContent = require( 'vscode-test-get-content' );

vscode.workspace.openTextDocument( __dirname + '/_fixtures/myFancyFile.txt' )
	.then( ( doc ) => {
		return vscode.window.showTextDocument( doc );
	} )
	.then( textEditor => {
		assert.equal( getContent( textEditor ), 'let text = "hello world!";' );
	} );

Getting the content with selections:

const vscode = vscode = require( 'vscode' ),
	getContent = require( 'vscode-test-get-content' );

vscode.workspace.openTextDocument( __dirname + '/_fixtures/myFancyFile.txt' )
	.then( ( doc ) => {
		return vscode.window.showTextDocument( doc );
	} )
	.then( textEditor => {
		// [, ], { and } characters mark a ranged selection.
		textEditor.selection = new vscode.Selection( 0, 4, 0, 8 );
		assert.equal( getContent.withSelection( textEditor ), 'let [text} = "hello world!";' );
	} );

Options

Both main getContent and withSelection methods take optional options object as a second argument.

  • options.normalizeEol - Boolean - Whether to change Windows-style end of line characters, to Unix-style. Defaults to true.
  • options.caret - String - Character used to represent caret (collapsed selection). Defaults to "^".
  • options.anchor.start - String - Selection anchor open character. Defaults to "[".
  • options.anchor.end - String - Selection anchor close character. Defaults to "]".
  • options.active.start - String - Selection active part open character. Defaults to "{".
  • options.active.end - String - Selection active part close character. Defaults to "}".

Selection Markers

There are three selection markers:

  • ^ - Marks a collapsed selection. This is ^random text
  • [, ] - Marks a ranged selection anchor point, so the place where ranged selection is started. This [is random} text
  • {, } - Marks a ranged selection active point, so the place selection ends. This [is random} text

Markers Customization

If the default makers collide with your test case, you can use custom markers by passing options object, just like below:

const vscode = vscode = require( 'vscode' ),
	getContent = require( 'vscode-test-get-content' );

vscode.workspace.openTextDocument( __dirname + '/_fixtures/myFancyFile.txt' )
	.then( ( doc ) => {
		return vscode.window.showTextDocument( doc );
	} )
	.then( textEditor => {
		let options = {
			caret: '🍕',
			active: {
				start: '🚒',
				end: '🚒'
			},
			anchor: {
				start: '🦄',
				end: '🦄'
			}
		};

		textEditor.selection = new vscode.Selection( 0, 4, 0, 8 ); // Select "text"" word.
		assert.equal( getContent.withSelection( textEditor, options ), 'let 🦄text🚒 = "hello world!";' );
	} );

Related

If you need to easily set your content with or without selection, be sure to check vscode-test-set-content package. It follows the same idea, and allows you to set the content and selection in similarly easy way.