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

ost-generator

v1.0.1

Published

Generates Offline Symbol Tables from source code

Downloads

5

Readme

ost-generator

oclif Version Downloads/week License

Illuminated Cloud users developing 2GP Apex development for a single namespace using multiple repositories might have run into the limitation of not having code-completion when calling @NamespaceAccessible code between the different namespaces. This is due to the fact that IC's Offline Symbol Table cannot pick up Namespace Accessible classes, as Salesforce obfuscates any code that is not global.

This tool is intended to provide a workaround, by updating the Offline Symbol Table using the local source files for the repository that contains the code for which auto-completion is required.

Install

npm install --global ost-generator

Usage

Imagine you have two 2GP packages, Package A and Package B. Package A contains @NamespaceAccessible methods that you wish to reference from Package B and get IC auto-completion.

You can achieve this as follows:

  1. Clone Package A locally
  2. Clone Package B locally
  3. cd into the root of Package B and run the following:
generate-ost 
    -namespace "abc" \
    -src "../Package_A/src" \
    --ostPath "IlluminatedCloud/PackageB/OfflineSymbolTable.zip"

WARNING: You might need to close IC while executing this command, because the OfflineSymbolTable might be locked by the OS when IC is open, and will not be modifiable.

Note that if you rebuild the Offline Symbol Table through IC, you will lose the updates and will need to re-run the command.

Arguments

namespace: The namespace that the packages share between them. src: The source directory with Apex code for which you wish to update the OST ostPath: The path to the Offline Symbol Table zip file that you wish had the src auto-completion.

$ npm install -g ost-generator
$ generate-ost COMMAND
running command...
$ generate-ost (-v|--version|version)
ost-generator/1.0.1 win32-x64 node-v12.17.0
$ generate-ost --help [COMMAND]
USAGE
  $ generate-ost COMMAND
...