executable name for windows

Open
  • Is something wrong?
#81 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
elixir
Domain
build-system

Research direction

Read the esbuild integration’s Windows executable naming logic and compare it with the Tailwind fix referenced in #140, where the executable suffix is handled separately from the target identifier. Check the related tests or run the Windows-specific tests; done means the esbuild executable is resolved correctly on Windows.

Written by the indexing model from the issue text.

Description

First of all, thank you for all the work you've put into this project and for recently fixing the Tailwind Windows executable naming issue. The fix works great there.

However, it looks like a very similar issue still exists in the esbuild integration on Windows. This appears to be the same type of issue that was recently fixed for Tailwind in #140, where the executable suffix is handled separately from the target identifier.

Thanks again for maintaining the project.

Dominant language
Elixir
Stars
276
Forks
42
Avg merge
1m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 phoenixframework/esbuild

All issues in phoenixframework/esbuild

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.