Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Is it possible to install a node.js in a Laravel app? Question Question
Deployment fails for Rails App with App Platform - No such file or directory - /workspace/node_modules/.bin/webpack (Errno::ENOENT) Question Question

Question

DigitalOcean App, Laravel, npm run production fails

Posted October 14, 2020 2.5k views
Node.jsLaravelDigitalOcean App Platform

Are there any fixes to npm run prod fails on build? I would like to add this to ensure what is on the live server is always the production build and avoid forgetting doing that before doing a commit.

However, I get this error, which isn’t happening on my local machine, or other servers which are not through “App”:

Browserslist: caniuse-lite is outdated. Please run the following command: `npm update`
ERROR  Failed to compile with 1 errors12:32:00 AM

error  in ./resources/js/app.js

Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /workspace/node_modules/@babel/helper-compilation-targets/package.json
Add a comment
emilmoe
By:
emilmoe

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Is it possible to install a node.js in a Laravel app? Question Question
Deployment fails for Rails App with App Platform - No such file or directory - /workspace/node_modules/.bin/webpack (Errno::ENOENT) Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
snormoredo October 14, 2020

@emilmoe 👋

What does the build command look like that you’re running?

I tried creating the sample-laravel app, updated the build command to be npm run production, and the output looks successful, but I may not have the exact same app/dependencies as your app:

sample-laravel | 08:43:14 Running custom build command: npm run production
sample-laravel | 08:43:14 
sample-laravel | 08:43:14 > @ production /workspace
sample-laravel | 08:43:14 > cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
sample-laravel | 08:43:14 
sample-laravel | 08:43:16       Additional dependencies must be installed. This will only take a moment.
sample-laravel | 08:43:16  
sample-laravel | 08:43:16       Running: npm install vue-template-compiler --save-dev --production=false
sample-laravel | 08:43:16  
sample-laravel | 08:43:25       Okay, done. The following packages have been installed and saved to your package.json dependencies list:
sample-laravel | 08:43:25  
sample-laravel | 08:43:25       - vue-template-compiler
sample-laravel | 08:43:25  
sample-laravel | 08:43:31  DONE  Compiled successfully in 4960ms12:43:31 PM

I see some references to the output you posted in this SO thread and this GH issue, where both mention resolutions of npm update or upgrading babel dependencies, but it’s not clear if this is relevant to your app/dependencies without more details.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help