Dependencies not removed about serverless-nuxt HOT 4 CLOSED

One more,

serverless.yml

package:
  exclude:
    - assets/**
    - components/**
    - pages/**
    - node_modules/**/*.ts
    - node_modules/**/*.ts.map
    - node_modules/**/*.js.map
    - node_modules/**/*.css.map

from serverless-nuxt.

in my case,

.serverless directory

cloudformation-template-create-stack.json
cloudformation-template-update-stack.json (or not)
serverless-state.json
project-name.zip

.serverless/project-name.zip directory

.next/**
node_modules/**

...(nuxt root directories like below)...
assets/**
modules/**
pages/**
plugins/**

package.json
package-lock.json
nuxt.config.js

handler.js (lambda entry file)

from serverless-nuxt.

If it exceeds 110MB, it is most likely a font or image.

All static files created after webpack build in the plugin are uploaded to s3.

1. When installing font or image related packages by npm, run it with the `--dev` option.
2. If you use image or font files under /static, please move them all under /assets. And when using in vue, please use the path using webpack.

Example in CSS

.something {
  background-image: url(~assets/images/something.png);
}

Example in Vue

<template>
  <!-- (X) -->
  <!-- <img src="/static/something.png" /> -->
  <!-- (O) -->
  <img :src="require('~/assets/images/something.png')" />
</template>

from serverless-nuxt.

@hmaesta the issue with many of these Nuxt lambda helpers is they don't seem to be tested with real world applications of a reasonable size. If you add a bunch of deps that are huge but tree-shaken small during a nuxt build, you still can't upload your package to Lambda because it contains the raw non tree-shaken node_modules versions which quickly hit the 50MB Lambda@Edge limit on any reasonably complex project.

from serverless-nuxt.