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

@tangelo/tangelo-configuration-toolkit

v1.22.1

Published

Tangelo Configuration Toolkit is a command-line toolkit which offers support for developing a Tangelo configuration.

Downloads

59

Readme

tangelo-configuration-toolkit

Tangelo Configuration Toolkit is a command-line toolkit which offers support for developing a Tangelo configuration.

Installation

The toolkit requires NPM on Node.js® (at least version 18.x). An active or maintenance LTS release is recommended. After installing Node.js, you can install the latest version of the Tangelo Configuration Toolkit globally on your system using the following command:

npm i -g @tangelo/tangelo-configuration-toolkit

Usage

Get help for the available commands and see version:

tangelo-configuration-toolkit

Get help for a specific command, detailing all its arguments:

tangelo-configuration-toolkit <command>

Use the tct shorthand instead of tangelo-configuration-toolkit:

tct <command>

Config

Global

TCT requires a config file to work: ${userhome}/.tct/appconfig.json
Several commands, like the deploy command, require server connection information, which can be stored in here.

The contents looks like this (all properties are optional):

{
  "sharedConfigPath": "absolute/or/relative/path/to/folder/containing/shared/config",
  "servers": [{
    "config": {
      "port": 22,
      "parallel": 4,
      "username": "username",
      "remotedir": "/absolute/path/to/tangelo/config/folder/on/server"
    },
    "domains": ["domain.name.com"],
    "name": "name-for-local-deploy"
  }],
  "serverDefaults": {
    "config": {
      ...
    }
  }
  "defaultServer": "can be set to the name of e.g. your favorite dev server",
  "defaultDatabase": "can be set to the tnsname of e.g. your favorite dev server"
}

When passing a server name, tct will look for a full match with a name or a partial match (the start) with a domain.

oXygen

The build -x commands set projects transformation scenarios and masterfiles in the oXygen project file with the following functionality:

  • Will try to preserve manually added entries in the transformation scenarios and masterfiles
  • Will remove non existing masterfiles or masterfiles that start with a '_'
  • No masterfiles / scenarios will be added if their path match with oXygens hidden directory patterns

Debug

Save this in the root of your local clone as tct-dev.cmd:

@ECHO off
SETLOCAL
CALL :find_dp0

IF EXIST "%dp0%\node.exe" (
  SET "_prog=%dp0%\node.exe"
) ELSE (
  SET "_prog=node"
  SET PATHEXT=%PATHEXT:;.JS;=;%
)

"%_prog%"  "%dp0%\index.js" %*
ENDLOCAL
EXIT /b %errorlevel%
:find_dp0
SET dp0=%~dp0
EXIT /b

Then:

  • open a 'Javascript Debug Terminal' in VSCode
  • jump to a customer folder ( you can use tan-cust for this)
  • set a breakpoint
  • type (for instance): tct-dev d -c