question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error : unable to locate after build

See original GitHub issue

Hello, Someone can help me to resolve this :

After build : npm run build && npm run upload

apps-script-starter@4.18.0 build C:\Emeric\Polyvalence\gestion-polyvalence webpack

LOG from copy-webpack-plugin <e> unable to locate ‘C:\Emeric\Polyvalence\gestion-polyvalence\functions*.js’ at ‘C:\Emeric\Polyvalence\gestion-polyvalence\functions*.js’ <e> unable to locate ‘C:\Emeric\Polyvalence\gestion-polyvalence\src**.html’ at 'C:\Emeric\Polyvalence\gestion-polyvalence\src**.html’

  • 21 hidden lines

ERROR in unable to locate ‘C:\Emeric\Polyvalence\gestion-polyvalence\functions*.js’ at ‘C:\Emeric\Polyvalence\gestion-polyvalence\functions*.js’

ERROR in unable to locate ‘C:\Emeric\Polyvalence\gestion-polyvalence\src**.html’ at 'C:\Emeric\Polyvalence\gestion-polyvalence\src**.html’ npm ERR! code ELIFECYCLE npm ERR! errno 2 npm ERR! apps-script-starter@4.18.0 build: webpack npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the apps-script-starter@4.18.0 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
EmericHochartcommented, Jul 28, 2020

Issue For Window User :

new CopyWebpackPlugin({ patterns: [ { from: path.posix.join(path.resolve(__dirname,‘src’).replace(/\/g, ‘/’), ‘**/.html’), flatten: true, to: destination }, { from: ${src}/../appsscript.json, to: destination, }, { from: path.posix.join(path.resolve(__dirname,‘src’).replace(/\/g, ‘/’), '…/functions/.js’), to: destination, flatten: true, }, ], }),

Thanks to @lauthieb

0reactions
labnolcommented, Aug 31, 2020

Resolved in the new build. Thanks @Zireael13

Read more comments on GitHub >

github_iconTop Results From Across the Web

ERROR in unable to locate ... glob on fresh project #120
I found a partial solution in the Slack channel was to move the project folder out of the $GOPATH which made the error...
Read more >
Dockerfile build error: Unable to locate - Stack Overflow
I am trying to build the following Radare2 dockerfile ...
Read more >
Unable to locate package" Error on Ubuntu [Beginner's Tutorial]
This beginner tutorial shows how to go about fixing the E: Unable to locate package error on Ubuntu Linux.
Read more >
Why am I getting the build error "Unable to find package ...
I am using VS2022 and am in the process of upgrading my .NET Core website to .NET 6.0. I completed my project modifications,...
Read more >
Unable to locate component resource error — Angular builds
I came across this weird error some time back when one of my clients provided me with an Angular repository that was not...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found