serverless-plugin-typescript icon indicating copy to clipboard operation
serverless-plugin-typescript copied to clipboard

Serverless plugin for zero-config Typescript support

Results 125 serverless-plugin-typescript issues
Sort by recently updated
recently updated
newest added

Hi, I can't run `serverless deploy --verbose`without getting the following issue: ``` Error: EPERM: operation not permitted, unlink '.../.build/node_modules' at Object.unlinkSync (fs.js:951:3) at TypeScriptPlugin. (.../node_modules/serverless-plugin-typescript/src/index.ts:195:12) at Generator.next () at .../node_modules/serverless-plugin-typescript/dist/src/index.js:7:71...

- In `yarn.lock`, no package has typescript as a dependency - In `package.json` it's under `devDependencies` - In `serverless.yml` I have `excludeDevDependencies: true` Yet for some reason when I run...

question

Adds the `dereference` option to flatten symlinks when copying node_modules. This is useful in lerna environments which might symlink a node_module within the same project. https://github.com/jprichardson/node-fs-extra/blob/HEAD/docs/copy-sync.md

Hello, every time I change one of the typescript files, it takes about 20 seconds to compile. I am currently using the following tsconfig.json configuration: ``` { "compilerOptions": { "target":...

Fixes #170 #24 will copy, and not link, `./node_modules` into `./.build/node_modules` on Windows when a module is symlinked. This will eventually break `copyDependencies`, that assumes `./.build/node_modules` is not a directory.

I have a simple setup so far regarding a particular service. The serverless.yml is setup like so: ``` provider: name: aws runtime: nodejs6.10 functions: uploadAudio: handler: role: package: individually: true...

After seeing the performance of this plugin degrading I investigated and found out that dependencies where copied during packaging. This takes ages to complete. Normal packaging of project takes a...

Closes #180 This feature is behind a custom option which is turned off by default, so this PR is backwards compatible.

Plugin throws an error if `"incremental": true` is in your `tsconfig.json` This happens by default using Nest.js

As mentioned in the issue #260 I wanted to avoid copying all the dependencies during packaging. Depending of how many dependencies you have it can save a lot of time....