Bug: Incompatible with serverless-plugin-typescript
See original GitHub issueWhen I add serverless-plugin-typescript
to the project, I get some errors from typescript trying to unlink directories.
PR for a breaking build:
https://github.com/dustyjewett/serverless-jetpack/pull/1
(I wasn’t able to run yarn test:cli
before or after my changes, so I’m just assuming the tests break, as I’m able to run serverless package
in the test directory on master, but it fails in my branch)
Serverless: Compiling with Typescript...
Serverless: Typescript compiled.
Error --------------------------------------------------
Error: EISDIR: illegal operation on a directory, unlink '/mnt/5aa17a51-a0c2-414d-aca1-4b6a28f5f4a0/projects/serverless-jetpack/test/packages/monorepo/yarn/.build/node_modules'
at Object.unlinkSync (fs.js:956:3)
at TypeScriptPlugin.<anonymous> (/mnt/5aa17a51-a0c2-414d-aca1-4b6a28f5f4a0/projects/serverless-jetpack/test/packages/monorepo/yarn/node_modules/serverless-plugin-typescript/src/index.ts:195:12)
at Generator.next (<anonymous>)
at /mnt/5aa17a51-a0c2-414d-aca1-4b6a28f5f4a0/projects/serverless-jetpack/test/packages/monorepo/yarn/node_modules/serverless-plugin-typescript/dist/src/index.js:7:71
at new Promise (<anonymous>)
at __awaiter (/mnt/5aa17a51-a0c2-414d-aca1-4b6a28f5f4a0/projects/serverless-jetpack/test/packages/monorepo/yarn/node_modules/serverless-plugin-typescript/dist/src/index.js:3:12)
at TypeScriptPlugin.copyDependencies (/mnt/5aa17a51-a0c2-414d-aca1-4b6a28f5f4a0/projects/serverless-jetpack/test/packages/monorepo/yarn/node_modules/serverless-plugin-typescript/dist/src/index.js:166:16)
at TypeScriptPlugin.<anonymous> (/mnt/5aa17a51-a0c2-414d-aca1-4b6a28f5f4a0/projects/serverless-jetpack/test/packages/monorepo/yarn/node_modules/serverless-plugin-typescript/src/index.ts:45:20)
at Generator.next (<anonymous>)
at fulfilled (/mnt/5aa17a51-a0c2-414d-aca1-4b6a28f5f4a0/projects/serverless-jetpack/test/packages/monorepo/yarn/node_modules/serverless-plugin-typescript/dist/src/index.js:4:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Fixing serverless typescript, Types of property 'event' are ...
I've upgraded to serverless 3, running typescript. There is a type match error in the serverless configuration files since.
Read more >serverless-webpack - npm
A Serverless Framework plugin to build your lambda functions with Webpack. This plugin is for you if you want to use the latest...
Read more >Serverless Sentry - Serverless Framework: Plugins
This Serverless plugin simplifies integration of Sentry with the popular Serverless Framework and AWS Lambda. Currently we support Lambda Runtimes for ...
Read more >Serverless | Ts.ED - A Node.js and TypeScript Framework on ...
This Serverless plugin emulates AWS λ and API Gateway on your local machine to ... Declaring all routes in the serverless.yml file can...
Read more >serverless-offline/community - Gitter
Hi! anyone have successfully used the latest plugin to run typescript apps? ... But I am facing some issue w/ testing using the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I know this is closed but I had this exact issue on Jenkins after I added a new npm package to the project. Looks like Jenkins was persisting the old TS compiled files and link to the node_modules folder. What I did to solve it was deleting the output folder (my folder is named
.build
, so I just did arm -rf .build
) for the compiled files and then run serverless. Solve it for me.… I checked out your branch. With this diff:
Which completely removes
serverless-jetpack
under any condition and this package command:I get your error, which means it’s not jetpack specific I think:
Let’s maybe have you turn to a minimal repository that produces the issue specific to jetpack so I can clone it, install, and follow your steps to a jetpack-specific error? Thanks!