Support async replacement

Open
#95 5 comments 2 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
javascript
Domain
build-system

Research direction

The issue does not identify files, tests, or an entry point for replacement handling. Start by tracing how gulp-replace currently computes replacement text, then determine the expected async API and add coverage demonstrating that asynchronous replacement results are awaited.

Written by the indexing model from the issue text.

Description

This could be useful when doing an async calculation of the replacement text (for example, compiling some javascript, etc).
I could try to put together a PR this week :)

Dominant language
JavaScript
Stars
495
Forks
87
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 lazd/gulp-replace

All issues in lazd/gulp-replace

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.