Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

.sync API

Open
#72 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript
Domain
documentation

Research direction

Start with the README section covering the .sync API and review how its arguments are currently described. Add an example or two showing the expected .sync usage, including the empty-array case, and consider the issue resolved when a reader can follow the examples without encountering the reported confusion.

Written by the indexing model from the issue text.

Description

Just had a nasty issue that took .. a few hours of my life .. using .sync without anything passed, didn't realize an empty array was at least expected.

const plugin = require("tailwindcss/plugin");
const postcssJs = require("postcss-js");
const styles = require("../dist/styles");

module.exports = plugin(function ({ addComponents }) {
  let postcssJsProcess;
  postcssJsProcess = postcssJs.sync(); // ... []
  result = postcssJsProcess(styles);
  addComponents(result);
});

Any way to clarify the Readme a bit to add an example or two for .sync?

Dominant language
JavaScript
Stars
667
Forks
24
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from postcss/postcss-js

All issues in postcss/postcss-js

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.