feat: Export normalizePath from wxt module

[PatrykKuniczak]

Overview

I've exported normalizePath from wxt,
I was wondering if i should export unnormalizePath also, but i don't know.
And @aklinker1 let's tell me, if i need to document it(to let people know, this is exposed), if yes, how to do it, because it's overhelmed to find sth in that docs.

Manual Testing

Try to import it somewhere, and check if it works.

Related Issue

#2013 (comment)

[netlify]

✅ Deploy Preview for creative-fairy-df92c4 ready!

Name	Link
🔨 Latest commit	57e4334
🔍 Latest deploy log	https://app.netlify.com/projects/creative-fairy-df92c4/deploys/6988464434a2ca000870465e
😎 Deploy Preview	https://deploy-preview-2080--creative-fairy-df92c4.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[pkg-pr-new]

Open in StackBlitz

@wxt-dev/analytics

npm i https://pkg.pr.new/@wxt-dev/analytics@2080

@wxt-dev/auto-icons

npm i https://pkg.pr.new/@wxt-dev/auto-icons@2080

@wxt-dev/browser

npm i https://pkg.pr.new/@wxt-dev/browser@2080

@wxt-dev/i18n

npm i https://pkg.pr.new/@wxt-dev/i18n@2080

@wxt-dev/module-react

npm i https://pkg.pr.new/@wxt-dev/module-react@2080

@wxt-dev/module-solid

npm i https://pkg.pr.new/@wxt-dev/module-solid@2080

@wxt-dev/module-svelte

npm i https://pkg.pr.new/@wxt-dev/module-svelte@2080

@wxt-dev/module-vue

npm i https://pkg.pr.new/@wxt-dev/module-vue@2080

@wxt-dev/runner

npm i https://pkg.pr.new/@wxt-dev/runner@2080

@wxt-dev/storage

npm i https://pkg.pr.new/@wxt-dev/storage@2080

@wxt-dev/unocss

npm i https://pkg.pr.new/@wxt-dev/unocss@2080

@wxt-dev/webextension-polyfill

npm i https://pkg.pr.new/@wxt-dev/webextension-polyfill@2080

wxt

npm i https://pkg.pr.new/wxt@2080

commit: 57e4334

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.06%. Comparing base (c8e788e) to head (57e4334).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2080      +/-   ##
==========================================
+ Coverage   75.80%   76.06%   +0.26%     
==========================================
  Files         113      113              
  Lines        3050     3050              
  Branches      686      686              
==========================================
+ Hits         2312     2320       +8     
+ Misses        653      646       -7     
+ Partials       85       84       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[aklinker1]

I was wondering if i should export unnormalizePath also, but i don't know.

No until someone needs it. Keep the public API footprint minimal.

If i need to document it(to let people know, this is exposed), if yes, how to do it, because it's overhelmed to find sth in that docs.

It will be documented in the release notes when released. Just double check that it has a good JSDoc comment, since the API reference is auto-generated based on those.

[github-actions]

Thanks for helping make WXT better!