-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
specify output dir in dist #163
Conversation
…ackage info embed to avoid package.json path resolution sisue
just ran into this :) @evanderkoogh any chance of a merge? |
Why is the |
Oh whoops, that was for my local installation/deploy for a duct tape
solution, my b
…On Sun, Sep 8, 2024 at 12:57 PM Jacob Hands ***@***.***> wrote:
Why is the dist directory committed in this PR?
—
Reply to this email directly, view it on GitHub
<#163 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACBRBT7PHYXZCZ35VVJTTZVR6WZAVCNFSM6AAAAABNWVC66KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWG42TEOBXGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
looks like @evanderkoogh modded to solve, closing this PR |
Lol.. I was just about to leave a comment here that I had found another way to fix it.. but thanks for your effort none the less! |
is this fixed? It fails I am not sure where to go from here |
no it appears to still be borked. |
attn @evanderkoogh this still needs to be addressed. See the tsconfig changes in this PR. If you want I can re-PR with your versions changes and remove the whole dist mess from this |
updated tsconfig for esm + cjs to explicitly set output dirs; added package info embed to avoid package.json path resolution issue
Fixes #162
What this PR solves / how to test:
testing env:
to test:
npm create cloudflare@latest -- my-first-worker
cd my-first-worker
npm run dev
npm i @microlabs/otel-cf-workers
npm run dev
, should see error per import / resolution error #162