ReferenceError: core_1 is not defined

[MonroeBrianJ]

I followed the instructions in the readme. I added my initials to a console.info call then I ran the unit tests. It failed with this message. I don't have a clue yet what's wrong. I'm hoping somebody out there does. I'm running this on Ubuntu on Windows.

FAIL test/constructs.test.ts
● Test suite failed to run

ReferenceError: core_1 is not defined

  20 | }
  21 |
> 22 | export class ServerlessImageHandlerStack extends Stack {
     |                                                  ^
  23 |   constructor(scope: Construct, id: string, props: ServerlessImageHandlerStackProps) {
  24 |     super(scope, id, props);
  25 |

  at Object.<anonymous> (lib/serverless-image-stack.ts:22:50)
  at Object.<anonymous> (test/constructs.test.ts:8:1)

[lachlangordon]

Running into the same thing here. Went to work on fixes for my fork and suddenly running into the above. Worked fine a month ago

[dougtoppin]

@MonroeBrianJ @lachlangordon Using the current v6.1.0 release, I tried the same test where I modified a console.info in several files, ran the unit tests, and could not duplicate any core_1 sort of error. I could cause snapshot out of date warnings but no issue that would fail a unit test.

Can you retry your test and let us know if you can cause the error again with the current release?
If so, please include what changes you made to the release version.

[MonroeBrianJ]

Doug, Thank you so much for following up. Sorry, but I’ve long ago worked around the issue and the DEV environment I had is long gone. Brian From: Doug Toppin ***@***.***> Sent: Sunday, December 18, 2022 2:47 PM To: aws-solutions/serverless-image-handler ***@***.***> Cc: MonroeBrianJ ***@***.***>; Mention ***@***.***> Subject: Re: [aws-solutions/serverless-image-handler] ReferenceError: core_1 is not defined (Discussion #376) @MonroeBrianJ <https://github.com/MonroeBrianJ> @lachlangordon <https://github.com/lachlangordon> Using the current v6.1.0 release, I tried the same test where I modified a console.info in several files, ran the unit tests, and could not duplicate any core_1 sort of error. I could cause snapshot out of date warnings but no issue that would fail a unit test. Can you retry your test and let us know if you can cause the error again with the current release? If so, please include what changes you made to the release version. — Reply to this email directly, view it on GitHub <#376 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXTHCO32HMYIPUUR53TD27LWN6A57ANCNFSM52HUZNLQ> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AXTHCO3AJIARQ5TPYRDDFMLWN6A57A5CNFSM52HUZNL2YY3PNVWWK3TUL52HS4DFWFCGS43DOVZXG2LPNZBW63LNMVXHJKTDN5WW2ZLOORPWSZGOABB43SQ.gif> Message ID: ***@***.*** ***@***.***> >