-
Notifications
You must be signed in to change notification settings - Fork 1
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
ESM plugins do not work with begin dev #154
Comments
Under the hood it is just an import statement. As such, paths need to include file names. |
Let's document this |
It still fails with a full filename for
You get the same error. |
|
See also: vercel/pkg#1291 |
What a nightmare. |
Indeed, apologies for the early closure of the issue @ryanbethel, Brian and I had worked through another esm plugin issue (the file name) from this repo already, I assumed it was the same. So I think the answer here for now is: Begin CLI currently does not support ESM plugins (due to limitations in pkg). Thoughts? |
It's frustrating that we are in a situation with Note: this is me being frustrated with |
its a deep sunk cost discussion but i feel like we should embrace |
Added better error handling when ESM plugins fail in pkg-compiled binary distributions; it's not a real fix, but it's at least a bit less bewildering! |
ESM plugins don't work with the Begin CLI using
begin dev
. They do, however, work when usingsandbox
directly.Steps to reproduce:
Using @brianleroux 's S3 upload repo at https://github.com/brianleroux/enhance-example-s3-upload .
git clone https://github.com/brianleroux/enhance-example-s3-upload.git
npm i
begin dev
npm i @architect/sandbox
npx sandbox
You should see the following error when running
begin dev
but no error runningnpx sandbox
:The text was updated successfully, but these errors were encountered: