Replies: 1 comment 4 replies
-
@ReintB Could you share your code base or a minimal reproduction? Also if I can ask what's going on with all the deprecated babel transforms and polyfills? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
[00:51:17.781] Running build in Washington, D.C., USA (East) – iad1
[00:51:17.934] Cloning github.com/ReintB/mini-ecommerce (Branch: main, Commit: 4db26b1)
[00:51:18.453] Previous build cache not available
[00:51:18.632] Cloning completed: 697.082ms
[00:51:18.932] Running "vercel build"
[00:51:19.823] Vercel CLI 34.2.7
[00:51:21.649] Installing dependencies...
[00:51:38.981] npm WARN deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
[00:51:39.064] npm WARN deprecated @babel/plugin-proposal-numeric-separator@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
[00:51:39.083] npm WARN deprecated @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
[00:51:39.084] npm WARN deprecated @babel/plugin-proposal-private-methods@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.
[00:51:39.105] npm WARN deprecated domexception@2.0.1: Use your platform's native DOMException instead
[00:51:39.188] npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
[00:51:39.191] npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
[00:51:39.192] npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
[00:51:39.344] npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[00:51:39.515] npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
[00:51:39.547] npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
[00:51:39.636] npm WARN deprecated @babel/plugin-proposal-nullish-coalescing-operator@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
[00:51:40.214] npm WARN deprecated @babel/plugin-proposal-optional-chaining@7.21.0: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
[00:51:40.221] npm WARN deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
[00:51:40.692] npm WARN deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
[00:51:40.726] npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
[00:51:41.402] npm WARN deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
[00:51:41.403] npm WARN deprecated
[00:51:41.403] npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
[00:51:41.571] npm WARN deprecated workbox-cacheable-response@6.6.0: workbox-background-sync@6.6.0
[00:51:41.713] npm WARN deprecated workbox-google-analytics@6.6.0: It is not compatible with newer versions of GA starting with v4, as long as you are using GAv3 it should be ok, but the package is not longer being maintained
[00:51:43.230] npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
[00:51:48.106]
[00:51:48.107] added 1543 packages in 26s
[00:51:48.107]
[00:51:48.108] 262 packages are looking for funding
[00:51:48.108] run
npm fund
for details[00:51:48.108] npm notice
[00:51:48.108] npm notice New minor version of npm available! 10.5.0 -> 10.8.1
[00:51:48.108] npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.1
[00:51:48.109] npm notice Run
npm install -g npm@10.8.1
to update![00:51:48.109] npm notice
[00:51:48.155] Detected
package-lock.json
generated by npm 7+[00:51:48.156] Running "npm run build"
[00:51:48.404]
[00:51:48.405] > mini-ecommerce@0.1.0 build
[00:51:48.406] > react-scripts build
[00:51:48.406]
[00:51:49.395] Creating an optimized production build...
[00:51:52.536] �[0;33mOne of your dependencies, babel-preset-react-app, is importing the
[00:51:52.537] "@babel/plugin-proposal-private-property-in-object" package without
[00:51:52.537] declaring it in its dependencies. This is currently working because
[00:51:52.537] "@babel/plugin-proposal-private-property-in-object" is already in your
[00:51:52.537] node_modules folder for unrelated reasons, but it �[1mmay break at any time�[0;33m.
[00:51:52.537]
[00:51:52.537] babel-preset-react-app is part of the create-react-app project, �[1mwhich
[00:51:52.538] is not maintianed anymore�[0;33m. It is thus unlikely that this bug will
[00:51:52.538] ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
[00:51:52.538] your devDependencies to work around this error. This will make this message
[00:51:52.538] go away.�[0m
[00:51:52.538]
[00:52:02.237] Failed to compile.
[00:52:02.239]
[00:52:02.239] [eslint]
[00:52:02.239] src/Recommended/Recommended.js
[00:52:02.239] Syntax error: Unexpected token (14:1) (14:1)
[00:52:02.239]
[00:52:02.239] src/Sidebar/Category/Category.js
[00:52:02.239] Syntax error: Unexpected token (19:1) (19:1)
[00:52:02.239]
[00:52:02.239] src/Sidebar/Colors/Colors.js
[00:52:02.239] Syntax error: Unexpected token (16:1) (16:1)
[00:52:02.239]
[00:52:02.239]
[00:52:02.283] Error: Command "npm run build" exited with 1
[00:52:02.632]
Excuse me everyone, here I am experiencing problems when I want to deploy my ReactJS project to Vercel. Here there are several errors such as:
Why am I experiencing an error like above? And what can I do to get this error resolved. Thank you very much
Example
No response
Steps to Reproduce
Maybe if one of my friends here can help me, I would be happy to hear a solution. Maybe you can discuss it in this forum. Once again, thank you so much
Beta Was this translation helpful? Give feedback.
All reactions