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

cv-tools

v1.1.0

Published

Framework to iterate over LaTeX documents and uploading to S3

Downloads

6

Readme

cv-tools

A set of gulp tasks to manage, package, and share LaTeX documents.

What is this?

I created this set of gulp tasks to help me manage my CV. I write my CV in LaTeX and publish it on S3 via a password protected zip archive.

I thought this workflow might be helpful to someone else, so I open sourced the tool.

Note that the tool will also work with any LaTeX document that you might want to make publicly available and password protected.

For some context about why I wrote this tool and how I'm using it, check out this article on Medium: https://medium.com/@coaxial/how-i-manage-my-cv-with-latex-gulp-s3-and-bitly-99694c01dd8

Assumptions

  • Your document is written using LaTeX
  • You want a publicly accessible, passworded protected version of your document
  • You want this publicly accessible version to be hosted on S3
  • You have a working npm and node (v4 or v6) install

Configuration

The tool uses two configuration files: config.json and aws_config.json. I suggest you use the example files config.example.json + aws_config.example.json as templates. When you're done, save a copy and remove .example from the filenames.

config.json

Configuration options for the tool itself

| Option | Usage | | ------------------ | ------------------------------------------------------------------ | | resume_filename | The LaTeX filename for your resume within src_dir (see below) | | archive_filename | Name used for the resulting compressed, password protected archive | | dist_dir | Relative path to the directory where the archive will be saved to | | src_dir | Relative path to the directory where your LaTeX files live |

If you're not using the default for src_dir, remember to add it to your .gitignore

aws_config.json

Contains AWS specific configuration options

| Option | Usage | | ---------| ----------------------------------------------- | | key | Your AWS key | | secret | Your AWS secret | | bucket | Name for the S3 bucket to upload the archive to | | region | Which AWS region to save your archive in (cf. https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) |

If you are unfamiliar with S3, AWS' documentation is a good starting point: https://aws.amazon.com/documentation/s3/

CV files

The tool expects your LaTeX files to be located in the src_dir specified in config.json. You can also add any custom LaTeX document class files needed to build your document in this directory, pdflatex will look for them there.

To illustrate, here is what my src_dir directory looks like:

src/
├── coaxialcv.cls
├── coaxial.pdf
└── coaxial.tex

If you version control your LaTeX files, you can git clone your repo in src_dir with $ git clone user/repo src/. You'll then be able to work on your document from within the tool's repo while committing changes to the documents repo.

Usage

| Gulp task | Usage | | --- | --- | | work | Gulp will watch for changes in src_dir and recompile to PDF. | | publish | Will package, password protect, and upload the document to S3 |

While using the work task, I suggest opening the PDF file in a PDF viewer on half of your monitor, and your text editor on the other half. As you save your document in the text editor, the PDF view will update almost instantly, and you'll see the changes right away without switching windows.

There are a few other plumbing tasks that the porcelain tasks above depend on. All of them are located in tasks/, I modularized to help with maintenance and readability. This is where to look if you're curious about how the tool works under the hood.

Contributions

Yes please! Fork the repo, make your changes, update the README if needed, and make a pull request. Make sure your tests pass against Node v4 and Node v6 both; make sure you use modularization when appropriate, ES6, and promises.

Issues

If you have a question or an issue using the tool, open a GitHub issue for help.

License

MIT (c) Coaxial 2016