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

@import url?

Open
#74 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
css, javascript
Domain
frontend, tooling

Research direction

The issue points to the stylelint example and asks about the rebase option in postcss-url. Start by reading that example and the option's documentation; done means determining whether rebase preserves @import references or copies CSS, then documenting the supported behavior or clarifying the limitation.

Written by the indexing model from the issue text.

Description

I see in this example an @import url(file.css) and I'm not whats going on there. Then I looked here and I see rebase as an option. Not sure what any of this does but it seems useful. Ideally importing CSS from postcss would be the same as importing CSS from JS where the reference gets reused rather than copied wholesale into the file creating duplication. Is that what rebase does?

Dominant language
JavaScript
Stars
383
Forks
58
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-url

All issues in postcss/postcss-url

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.