Comments on: Magento 2 Javascript Bundling with Magepack

By: Ram

Ram — Thu, 15 Dec 2022 10:06:27 +0000

mageback bundle -m command is only working if we run on command line, but if we try to run this command via Jenkins ansible script getting below error

[Errno 2] No such file or directory

Any idea on this?

By: Ram

Ram — Thu, 15 Dec 2022 10:02:45 +0000

Try this with speed network

By: helmi

helmi — Fri, 12 Aug 2022 09:54:15 +0000

why Magepack does not bundle all JS ?
I added some js to magepack.config.js file, but magepack doesn’t support these js when doing the bundling.
can you help me?

By: Janko Hrasko

Janko Hrasko — Fri, 09 Jul 2021 09:09:50 +0000

Collecting modules for bundle “category”. 09:06:47

ERROR waiting for function failed: timeout 60000ms exceeded 09:07:48

at new WaitTask (/usr/lib/node_modules/magepack/node_modules/puppeteer/lib/DOMWorld.js:549:28)
at DOMWorld.waitForFunction (/usr/lib/node_modules/magepack/node_modules/puppeteer/lib/DOMWorld.js:454:12)
at Frame.waitForFunction (/usr/lib/node_modules/magepack/node_modules/puppeteer/lib/FrameManager.js:657:28)
at Page.waitForFunction (/usr/lib/node_modules/magepack/node_modules/puppeteer/lib/Page.js:1141:29)
at module.exports (/usr/lib/node_modules/magepack/lib/generate/collectModules.js:12:16)
at Object.category (/usr/lib/node_modules/magepack/lib/generate/collector/category.js:40:39)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async module.exports (/usr/lib/node_modules/magepack/lib/generate.js:24:13)

I found this :
// Since page navigation requires us to re-install the pageScript, we should track
// timeout on our end.
if (timeout) {
const timeoutError = new TimeoutError(`waiting for ${title} failed: timeout ${timeout}ms exceeded`);
this._timeoutTimer = setTimeout(() => this.terminate(timeoutError), timeout);
}
this.rerun();

Whats the problem?

By: Janko Hrasko

Janko Hrasko — Fri, 09 Jul 2021 09:08:55 +0000

Or whats the problem? I found this :

// Since page navigation requires us to re-install the pageScript, we should track
// timeout on our end.
if (timeout) {
const timeoutError = new TimeoutError(`waiting for ${title} failed: timeout ${timeout}ms exceeded`);
this._timeoutTimer = setTimeout(() => this.terminate(timeoutError), timeout);
}
this.rerun();

By: Janko Hrasko

Janko Hrasko — Fri, 09 Jul 2021 09:01:18 +0000

Collecting modules for bundle “category”. 08:54:43

ERROR waiting for function failed: timeout 30000ms exceeded 08:55:14

Where can I set timeout?

By: Haritha

Haritha — Wed, 23 Jun 2021 06:57:37 +0000

In reply to Solteq.

Hi Solteq,

While trying to implement in the build phase of .magento.app.yaml, it results in issue below as the static content deployment is running after the build phase. Is there fix for this?
—————————————————————————————————————-
W: ERROR No locales found! Make sure magepack is running after static content is deployed.
—————————————————————————————————————-

By: PAJ

PAJ — Tue, 16 Mar 2021 08:12:42 +0000

In reply to Cristian. You are returning true with if self::XML_PATH_ENABLE_MAGEPACK_BUNDLING before the checkout logic can function. The checkout logic must occur before the module enabled check.

By: Cristian

Cristian — Mon, 15 Mar 2021 20:03:08 +0000

In reply to PAJ.

I need to disable checkout and put my isEnabled like this:
public function isEnabled()
{
return $this->scopeConfig->isSetFlag(
self::XML_PATH_ENABLE_MAGEPACK_BUNDLING,
ScopeInterface::SCOPE_STORE
);
if ($this->request->getFullActionName() == ‘checkout_index_index){

// disable for checkout
return false;
}
}
But, the checkout continues to be optimized

By: Brandon Irwin

Brandon Irwin — Mon, 08 Mar 2021 18:03:50 +0000

You mentioned you were in docker running magepack on your php container.

I have followed the docs using the php docker container but when i run magepack generate –debug it gives me a failed to launch the browser process.

Have you ran into this?