Error after npm update
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- babel, javascript, node.js, wordpress
- Domain
- build-system
Research direction
Reproduce the failure by running npm update followed by npm start, then inspect assets/js/spacing-control.js alongside the Babel clone-deep stack trace. Determine what dependency state allows npm start to complete successfully; done means the Parcel watch command runs without this cloning error.
Written by the indexing model from the issue text.
Description
After installing, I run npm start and am prompted to run npm update. I do that, and then npm start again. This error is generated:
$ npm start
(node:28902) ExperimentalWarning: The fs.promises API is experimental
> [email protected] start
> parcel watch --no-hmr assets/js/extend-block-example.js -d dist
🚨 Git/extend-block-example-wp-plugin/assets/js/spacing-control.js: function __clone() {
var node2 = new Node();
for (var key in this) {
// Do not clone comments tha...<omitted>... } could not be cloned.
var node2 = new Node();
for (var key in this) {
// Do not clone comments tha...<omitted>... } could not be cloned.
at Object.serialize (v8.js:202:7)
at _default (Git/extend-block-example-wp-plugin/node_modules/@babel/core/lib/transformation/util/clone-deep.js:22:34)
at normalizeFile (Git/extend-block-example-wp-plugin/node_modules/@babel/core/lib/transformation/normalize-file.js:84:36)
at normalizeFile.next (<anonymous>)
at run (Git/extend-block-example-wp-plugin/node_modules/@babel/core/lib/transformation/index.js:29:50)
at run.next (<anonymous>)
at Function.<anonymous> (Git/extend-block-example-wp-plugin/node_modules/@babel/core/lib/transform-ast.js:26:41)
at Generator.next (<anonymous>)
at evaluateSync (Git/extend-block-example-wp-plugin/node_modules/gensync/index.js:251:28)
at Function.sync (Git/extend-block-example-wp-plugin/node_modules/gensync/index.js:89:14)
- Dominant language
- JavaScript
- Stars
- 50
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from liip/extend-block-example-wp-plugin
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
All issues in liip/extend-block-example-wp-plugin
Similar issues
-
ai-proposed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area: certificates help wanted priority: must type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WNSolutions/digimenu-tn#35 ·
-
bug priority: low
Difficulty 1/5 Under an hour Newbie friendliness 88/100
sandialabs/sceptre-phenix#464 ·
Maintainers usually reply within 6 days
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
hemilabs/token-list#124 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day