Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Build error with version 2.6.0: @parcel/core: Failed to resolve 'buffer' from ... #8223

Closed
liby opened this issue Jun 17, 2022 · 1 comment
Closed
Labels
Stale Inactive issues

Comments

@liby
Copy link

liby commented Jun 17, 2022

🐛 bug report

🎛 Configuration (.babelrc, package.json, cli command)

.babelrc: none

package.json(Only the relevant parts are listed)

{
  "packageManager": "pnpm@7.2.1",
  "engines": {
    "node": ">=16.0.0",
    "pnpm": ">=7.0.0",
    "yarn": ">2 <1",
    "npm": ">2 <1"
  },
  "source": "admin/index.html",
  "browserslist": "> 0.5%, last 2 versions, not dead",
  "scripts": {
    "start": "concurrently -k \"netlify-cms-proxy-server\" \"ws -d admin --static.index index.dev.html -p 5001 -o\"",
    "admin:build-dev": "parcel ./admin/index.html",
    "admin:build": "parcel build ./admin/index.html --dist-dir admin_dist --public-url=/shared",
    "prebuild": "ts-node ./src/prebuild.ts",
    "build": "tsc"
  }
}

🤔 Expected Behavior

Build should pass.

😯 Current Behavior

Details
❯ pnpm run admin:build

> @right/config@1.0.0 admin:build /Users/user/Code/example
> parcel build ./admin/index.html --dist-dir admin_dist --public-url=/shared

[Error: ENOENT: no such file or directory, open '/Users/user/Code/example/node_modules/.pnpm/netlify-cms-app@2.15.72_@types+node@17.0.45/node_modules/netlify-cms-app/dist/webpack:/NetlifyCmsApp/Users/erezrokah/Code/github/netlify-cms/node_modules/js-base64/base64.mjs'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/user/Code/example/node_modules/.pnpm/netlify-cms-app@2.15.72_@types+node@17.0.45/node_modules/netlify-cms-app/dist/webpack:/NetlifyCmsApp/Users/erezrokah/Code/github/netlify-cms/node_modules/js-base64/base64.mjs'
}
⠋ Building index.js...
[Error: ENOENT: no such file or directory, open '/Users/user/Code/example/node_modules/.pnpm/netlify-cms-app@2.15.72_@types+node@17.0.45/node_modules/netlify-cms-app/dist/webpack:/NetlifyCmsApp/Users/erezrokah/Code/github/netlify-cms/node_modules/js-base64/base64.mjs'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/user/Code/example/node_modules/.pnpm/netlify-cms-app@2.15.72_@types+node@17.0.45/node_modules/netlify-cms-app/dist/webpack:/NetlifyCmsApp/Users/erezrokah/Code/github/netlify-cms/node_modules/js-base64/base64.mjs'
🚨 Build failed.

@parcel/core: Failed to resolve 'buffer' from './node_modules/.pnpm/netlify-cms-app@2.15.72_@types+node@17.0.45/node_modules/netlify-cms-app/dist/netlify-cms-app.js'

  /Users/user/Code/example/node_modules/.pnpm/netlify-cms-app@2.15.72_@types+node@17.0.45/node_modules/netlify-cms-app/dist/netlify-cms-app.js:19:27
    18 |  * is-plain-object <https://github.com/jonschlinkert/is-plain-object>
  > 19 |  *
  >    |   ^
    20 |  * Copyright (c) 2014-2017, Jon Schlinkert.
    21 |  * Released under the MIT License.

@parcel/resolver-default: Failed to install buffer: pnpm failed to install modules

  Error: Failed to install buffer: pnpm failed to install modules
      at $32ea97b83cf5d752$var$install (/Users/user/Code/example/node_modules/.pnpm/@parcel+package-manager@2.6.0_@parcel+core@2.6.0/node_modules/@parcel/package-manager/lib/index.js:3688:15)
      at async $b0fd219fea43bcac$export$2e2bcd8739ae039._runFn (/Users/user/Code/example/node_modules/.pnpm/@parcel+utils@2.6.0/node_modules/@parcel/utils/lib/index.js:32339:13)
      at async $b0fd219fea43bcac$export$2e2bcd8739ae039._next (/Users/user/Code/example/node_modules/.pnpm/@parcel+utils@2.6.0/node_modules/@parcel/utils/lib/index.js:32332:9)

 ELIFECYCLE  Command failed with exit code 1.

💁 Possible Solution

n/a

🔦 Context

Related issue: #7697

💻 Code Sample

n/a

🌍 Your Environment

Software Version(s)
Parcel 2.6.0
Node 16.13.2
npm/Yarn pnpm@v7.2.1
Operating System macOS@12.3.1
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.

@github-actions github-actions bot added the Stale Inactive issues label Dec 14, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Stale Inactive issues
Projects
None yet
Development

No branches or pull requests

1 participant