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

@syncify/config

v0.0.4

Published

Project-level defineConfig utiltity for usage with global installations of Syncify

Downloads

278

Readme

!! ATTENTION - PLEASE READ !!

This module is intended for users leveraging JavaScript or TypeScript configuration files with global installations of the Syncify CLI. Developers using project installations do not require this package.

@syncify/config

This utility provides a project-level defineConfig function specifically for use within syncify.config.js (or .ts) configuration files. It is made available for users working on Shopify themes using global Syncify CLI installations.

Why?

Globally installed Node packages are only available as CLI binaries. If you are using .js or .ts configuration files to define per-project settings for Syncify, global installations of the module will prevent TypeScript features from working at the project-level. This module patches that limitation by exposing the defineConfig utility in isolation.

Installation

Please ensure you have global installation of @syncify/cli available on your system. If you are using a local installation of the CLI (i.e, within your devDependencies or depedencies list), you already have access to the defineConfig utility and you do not need this module.

pnpm add @syncify/config -D

Usage

The module exposes a defineConfig named export function and env reference model which you can use within you syncify.config.js or syncify.config.ts file. This is indentical to the defineConfig and env named export available within @syncify/cli. package.

import { defineConfig, env } from '@syncify/config';

env.dev    // boolean
env.prod   // boolean
env.watch  // boolean

export default defineConfig({
  hot: {},
  log: {},
  clean: true,
  editor: 'vscode',
  input: 'source',
  output: 'theme',
  import: 'import',
  export: 'export',
  config: '.',
  paths: {},
  transform: {},
  processors: {},
  versioning: {}
})

As mentioned several times in this readme, those who have local installs of @syncify/cli (i.e, it exists in your projects devDependencies object) do not need to install this package. You can access the same defineConfig named export within the @syncify/cli module.

Contributing

This package is designed for usage within Syncify and version increments are applied in automation. Contributions are not accepted unless they pertain to the core Syncify module. If contributions fall into that category, fork the entire Syncify project.