errors running `solid-start start` ->. some aws deps -> no issues with dev mode

[quantuminformation]

having fun with aws

we not using AWS, so no ideas about that one

and another one we have no idea about

[quantuminformation]

bcryptjs removed one error

[Bramas]

Hi, I have the same error presented here #481 It seems the build process is broken when some packages are used (also introducing errors that are unrelated like this aws package) In my issue i presented a very simple way to reproduce.

[Bramas]

I solved my problem here #481

I think you should just add some packages in the file vite.config.ts: add the option:

ssr: {
    external: ["LIB1", "LIB2"],
  }

where LIB* are native packages that introduced the error (not mock-aws-s3, but some packages in your package.json, maybe the best way is to put them all here and try to remove them one by one)

[ryansolid]

Yeah these stack trace actually say very little. I'd recommend externalizing the dependencies and leaving node to do its thing here. It looks like these are perhaps cjs and there is challenges importing it with esm. Also no idea on the AWS dep. If that doesn't work need a reproduction.

[OrJDev]

If you are using bcrypt, it should be externalized (and bcrypt is using nock and mock-aws-3), so this is probably where this is coming from.

[ryansolid]

In setting up for SolidStarts next Beta Phase built on Nitro and Vinxi we are closing all PRs/Issues that will not be merged due to the system changing. If you feel your issue was closed in mistake. Feel free to re-open it after updating/testing against 0.4.x release. Thank you for your patience.

See https://github.com/solidjs/solid-start/pull/1139 for more details.