Skip to content
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

hydrate undefined error for multiple paths on direct deploy #1455

Open
kenhorn opened this issue Oct 6, 2023 · 0 comments
Open

hydrate undefined error for multiple paths on direct deploy #1455

kenhorn opened this issue Oct 6, 2023 · 0 comments

Comments

@kenhorn
Copy link

kenhorn commented Oct 6, 2023

Describe the issue
./node_modules/@architect/hydrate/src/hydrate.js:123
if (lambdaHasManifest && lambda.config.runtime.startsWith('nodejs')) {
^
TypeError: Cannot read properties of undefined (reading 'runtime')
at ./node_modules/@architect/hydrate/src/hydrate.js:123:46

v10.10.3

If my app.arc contains two paths for a single source dir, ie:

/foo
method post
src src/http/post-foo

/foo-noauth
method post
src src/http/post-foo

I get the above error for direct deploys, but a normal deploy is fine. The lambda object has no config member, as in the above scenario it's an array of configs. Presumably something isn't calling .flatten() or similar for direct deploys.

Removing the second path's setup works as a workaround in dev.

Steps to reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error that says '....'

Expected behavior
A function should be deployed per normal / full deploy

Screenshots
If applicable, add screenshots to help explain your problem

Desktop
Please complete the following information (if appropriate):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Mobile
Please complete the following information (if appropriate):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context or notes about the problem here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant