retlehs
commented
3 weeks ago What are the minimal reproduction steps for this issue? I'm not seeing any actionable instructions provided
Open JUVOJustin opened 3 weeks ago
retlehs
commented
3 weeks ago What are the minimal reproduction steps for this issue? I'm not seeing any actionable instructions provided
JUVOJustin
commented
3 weeks ago @retlehs as i said, this only happens in this specific project. Feel free to clone it here: https://github.com/JUVOJustin/dynamic-forms. You can also see the latest action run tried building the assets, which failed for the same reason. I honestly cannot tell you how to reproduce this in another fresh project.
However, the error is very likely caused by bud since i already removed all other configs and dependencies and the same error keeps occurring as long as bud is installed.
JUVOJustin
commented
2 weeks ago I did some further digging. All of our projects are created using this boilerplate: https://github.com/JUVOJustin/wordpress-plugin-boilerplate/. It uses bud.js 6.20 and comes with a package-lock.json. When using the boilerplate exclusively with npm install bud works.
When upgrading bud.js either via npm update or by changing the version string and running npm install the mentioned error occurs. When downgrading back to 6.20 some packages are still changed when comparing the package-lock.json with the initial one from the boilerplate.
I am not the most familiar with JS, so for further debugging I would appreciate some guidance. To me from a more or less uneducated standpoint this seems to be an issue with any of the dependencies changed in 6.21, which due to some version constraints also gets not downgraded/removed when changing back to an older bud version.
The good thing is, that copying the boilerplates package-lock.json and running npm install does seem to be a workaround for downgrading.
acrobertson
commented
2 weeks ago I'm encountering this same issue in my project, and I was able to reproduce it by simply running npx create-bud-app (See Screenshot 1) and then immediately running the build command in the project. (See Screenshot 2.)
In case it's helpful, here's the full output of npx bud doctor:
bud doctor outputcreate-bud-appnpx bud build
amustill
commented
2 weeks ago I'm also experiencing this across a few projects and new projects created via create-bud-app.
It appears to be related to the bud-dashboard module, potentially from a breaking change in react-reconciler published a few days ago? Although I haven't dug deeper.
In the meantime I have found adding the --no-dashboard option works around the error.
ligne13
commented
2 weeks ago Same issue today. @amustill where do you add the option --no-dashboard ?
Thank you
amustill
commented
2 weeks ago On the command line. Your exact command may be slightly different depending on your setup, but something similar to:
npx bud dev --no-dashboard
If you've used npx create-bud-app then you can edit the two script commands package.json, eg:
"scripts": {
"build": "bud build production --no-dashboard",
"dev": "bud build development --no-dashboard"
},You lose some prettiness, but it works and you still get build outputs:
app:
6 assets
39 modules
app (webpack 5.89.0) compiled successfully in 419 ms
hejamartin
commented
3 days ago On the command line. Your exact command may be slightly different depending on your setup, but something similar to:
npx bud dev --no-dashboardIf you've used
npx create-bud-appthen you can edit the two script commandspackage.json, eg:"scripts": { "build": "bud build production --no-dashboard", "dev": "bud build development --no-dashboard" },You lose some prettiness, but it works and you still get build outputs:
app: 6 assets 39 modules app (webpack 5.89.0) compiled successfully in 419 ms
Thanks. That this has not been resolved yet is crazy. I am subscribing to this Issue, and hope soon to get an email ;)
johanmolen
commented
3 days ago Subscribing too, getting this error too since downgrading back to 6.20.
Agreement
Describe the issue
Whenever running development or build the function errors with
Cannot read properties of null (reading 'useState').Full console Output
Expected Behavior
Bundeling assets
Actual Behavior
Errors and does not bundle assets correctly
Steps To Reproduce
It is occurring only with one project. On the exact same vm i have another bud project with the very same setup which works as it is supposed to. Also, it does not matter which other dependencies are added. Once bud is added even if it is the only dependency, the error occurs.
version
any of the later versions tested with 6.21 and 6.20
Logs
Configuration
Relevant .budfiles
No response