执行npm run build构建Vuesax项目时core-js依赖缺失求助

I’ve tackled similar core-js/Babel compatibility headaches in legacy Vue projects, so let’s walk through actionable steps to get your build working:

1. Align Core-JS Version with Babel Configuration #

The error references paths like core-js/library/fn/array/from—this is the module structure specific to core-js@2, while core-js@3 uses core-js/es/array/from. Here’s how to fix the mismatch:

• Check your project’s Babel config (either babel.config.js or .babelrc):
  Look for @babel/preset-env settings, especially the useBuiltIns and corejs options. If useBuiltIns is set to usage or entry, ensure the corejs value matches the version listed in your package.json.
  Example valid config for core-js@2:

  module.exports = {
    presets: [
      ['@babel/preset-env', {
        targets: { browsers: 'last 2 versions' },
        useBuiltIns: 'usage',
        corejs: 2
      }]
    ]
  };
  

• If your package.json doesn’t list core-js, or has version 3 installed, explicitly add core-js@2:

  npm install core-js@2 --save
  

2. Fix Docker Dependency Installation #

Docker’s caching can trap outdated or broken dependencies. Let’s adjust your Dockerfile for consistency:

• Replace RUN npm install with RUN npm ci—this installs dependencies exactly as defined in package-lock.json, eliminating version mismatches.
• When building, add the --no-cache flag to force a fresh dependency install:

  docker build --no-cache -t vuesax-build .
  

• Double-check that both package.json and package-lock.json exist in your project root (your Dockerfile copies them, but it’s easy to accidentally ignore the lockfile).

3. Lock to a Specific Node.js Version #

Vuesax is a mature project, so newer Node LTS versions might introduce compatibility gaps. Instead of node:lts-alpine, use a version that matches the project’s original supported environment:

• Check the Vuesax repo’s package.json for the engines field (if present) to find the recommended Node version. For example, if it specifies node: ">=10 <13", update your Dockerfile to:

  FROM node:12-alpine
  

4. Verify Vue CLI Babel Configs #

If your project uses Vue CLI, check vue.config.js for custom Babel settings that might conflict with your root Babel config. Ensure there are no duplicate or misconfigured presets overriding core-js handling.

5. Clean Residual Files #

• On your local machine, delete node_modules and package-lock.json, then run npm install to generate a fresh lockfile before copying to Docker.
• Stop and remove any existing Docker containers/volumes linked to this build to clear leftover cached data.

内容的提问来源于stack exchange，提问作者Cutaraca