You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Critical Dependency Warnings:
During the build process, several warnings related to critical dependencies were observed:
File: ./node_modules/cosmiconfig/dist/loaders.js
File: ./node_modules/import-fresh/index.js
File: ./node_modules/typescript/lib/typescript.js
These warnings are linked to dynamic imports in the Puppeteer and related dependencies, potentially affecting build reliability.
Missing .local-chromium:
Puppeteer does not create the .local-chromium directory in node_modules due to updated behavior:
Shared Cache Directory: Chromium binaries are now stored in ~/.cache/puppeteer by default to reduce redundancy across projects.
Possible Causes:
Use of puppeteer-core instead of puppeteer.
Environment variables (PUPPETEER_SKIP_DOWNLOAD, PUPPETEER_CACHE_DIR) modifying download behavior.
Installation issues due to network or configuration errors.
Resolution Steps:
Addressing Critical Dependency Warnings:
Enable detailed error logs (--stats-error-details) for more insights.
Investigate and refactor any dynamic imports where feasible.
Restoring .local-chromium:
Set the PUPPETEER_CACHE_DIR to node_modules/puppeteer/.local-chromium.
Redownload Chromium using:
bash
Copy code
node node_modules/puppeteer/install.mjs
Packaging Chromium for Extensions:
Use tools like vsce to include .local-chromium in the package.
Address size limitations for the VS Code Marketplace (200 MB) using:
Platform-specific builds.
Dynamic Chromium downloads.
Debugging Chromium Path Issues:
Confirm Chromium’s executable path using Puppeteer’s API:
javascript
Copy code
const puppeteer = require('puppeteer');
console.log(puppeteer.executablePath());
Recommendations:
Use puppeteer (not puppeteer-core) for bundled Chromium unless a custom solution is needed.
Fine-tune .vscodeignore to manage package size efficiently.
For VS Code extensions, verify Chromium inclusion and test on clean environments.
Reproduction
Have only built our Mac supported bundle with chromium includes. Assuming similar issues will be encountered building chromium bundled version for Windows and Linux.
System information
npm run build
vsce package
Additional information
No response
👨👧👦 Contributing
🙋♂️ Yes, I'd love to make a PR to fix this bug!
The text was updated successfully, but these errors were encountered:
Description
Critical Dependency Warnings:
During the build process, several warnings related to critical dependencies were observed:
File: ./node_modules/cosmiconfig/dist/loaders.js
File: ./node_modules/import-fresh/index.js
File: ./node_modules/typescript/lib/typescript.js
These warnings are linked to dynamic imports in the Puppeteer and related dependencies, potentially affecting build reliability.
Missing .local-chromium:
Puppeteer does not create the .local-chromium directory in node_modules due to updated behavior:
Shared Cache Directory: Chromium binaries are now stored in ~/.cache/puppeteer by default to reduce redundancy across projects.
Possible Causes:
Use of puppeteer-core instead of puppeteer.
Environment variables (PUPPETEER_SKIP_DOWNLOAD, PUPPETEER_CACHE_DIR) modifying download behavior.
Installation issues due to network or configuration errors.
Resolution Steps:
Addressing Critical Dependency Warnings:
Enable detailed error logs (--stats-error-details) for more insights.
Investigate and refactor any dynamic imports where feasible.
Restoring .local-chromium:
Set the PUPPETEER_CACHE_DIR to node_modules/puppeteer/.local-chromium.
Redownload Chromium using:
bash
Copy code
node node_modules/puppeteer/install.mjs
Packaging Chromium for Extensions:
Use tools like vsce to include .local-chromium in the package.
Address size limitations for the VS Code Marketplace (200 MB) using:
Platform-specific builds.
Dynamic Chromium downloads.
Debugging Chromium Path Issues:
Confirm Chromium’s executable path using Puppeteer’s API:
javascript
Copy code
const puppeteer = require('puppeteer');
console.log(puppeteer.executablePath());
Recommendations:
Use puppeteer (not puppeteer-core) for bundled Chromium unless a custom solution is needed.
Fine-tune .vscodeignore to manage package size efficiently.
For VS Code extensions, verify Chromium inclusion and test on clean environments.
Reproduction
Have only built our Mac supported bundle with chromium includes. Assuming similar issues will be encountered building chromium bundled version for Windows and Linux.
System information
npm run build
vsce package
Additional information
No response
👨👧👦 Contributing
The text was updated successfully, but these errors were encountered: