I need some help with TS + Mocha, not specifically...
# typescriptl
little-cartoon-10569
03/22/2021, 10:57 PMI need some help with TS + Mocha, not specifically to do with Pulumi. I'm testing some Pulumi resource components, but I'm finding that my updated TS code (which is compiling correctly to the expected ./lib directory) isn't always being found. My beginner npm/node knowledge is hampering my investigation.
little-cartoon-10569
03/22/2021, 10:58 PMWhen I run my tests, the .ts code is correctly compiling. In the correct directory under ./lib, I can see the updated .d.ts files, .js iles, etc.
little-cartoon-10569
03/22/2021, 10:59 PMHowever when I then run Mocha, it's not finding new files. They're there, it's just reporting that it can't find them. I don't know if it's looking in the wrong place, or it's refusing to update some internal cache, or what.
little-cartoon-10569
03/22/2021, 11:01 PMWhat can I pare back to work towards finding the source of the problem? Should I try creating a .js file in my ./lib file and seeing if Mocha can find that?
little-cartoon-10569
03/22/2021, 11:04 PMI have
"lib": "./lib", "test": "."little-cartoon-10569
03/22/2021, 11:04 PMI haven't defined any "dependencies": everything is defined in "devDependencies".
little-cartoon-10569
03/22/2021, 11:11 PMThe error message always looks like this:
TypeError: Unable to require file: lib/test/mocha/pulumi/FileThatExists.spec.d.ts
little-cartoon-10569
03/23/2021, 3:01 AMI had some tweaks to defaults (e.g. location of .mocharc.json file) that I removed; I think everything is now in npm's and Mocha's opinionate preference locations. No more complaining about not finding files that exist.
little-cartoon-10569
03/23/2021, 3:02 AMUnfortunately, I'm now getting compile errors, but only if I specify a single spec file (
npm run test --spec **/Si*.spec.tsnpm run test --spec **/S*.spec.tslittle-cartoon-10569
03/23/2021, 3:03 AMWeeeeird.
little-cartoon-10569
03/23/2021, 3:04 AMAll the compile failures strictly sensible: I'm using code like
expect(bucketUnderTest.bucket.serverSideEncryptionConfiguration!.rule.applyServerSideEncryptionByDefault.sseAlgorithm.promise()).to.eventually.contain("kms")error TS2339: Property 'rule' does not exist on type 'Output<BucketServerSideEncryptionConfiguration | undefined>'.Property 'rule' does not exist on type 'OutputInstance<BucketServerSideEncryptionConfiguration | undefined>'.
little-cartoon-10569
03/23/2021, 3:04 AMNo idea why the complaints go away when I run the tests in more than one file, though.
little-cartoon-10569
03/23/2021, 3:05 AMOr how to fix the issue: the serverSideEncryptionConfiguration does exist, but I suppose the type can't be lifted out of
Output<BucketServerSideEncryptionConfiguration | undefined>little-cartoon-10569
03/23/2021, 3:06 AMIf anyone comes across this thread and has a suggestion, I'd love to hear it. For now, I'm going to lower the strictness of my linting when running tests. Which isn't ideal..
2 Views