Error parsing descriptor string in production environment
See original GitHub issueHi
First of all. Stimulus is great - thanks for sharing this with us. I’ve spent the day getting it into my Phoenix app which already uses turbolinks. It works great in my development environment 🎉.
After finishing up the intended work, I decided to ship it to our production environment. But it seems like the production build fails to setup the actions & targets. I assume it has something to do with minification of the javascript. 😢
I can’t find any information in the docs about this issue. I’m not using webpack. The stimulus instance is starting, and the controllers are connected properly. But the actions cannot be parsed.
Here’s an output of the stacktrace in Chrome.
Error parsing descriptor string "click->card-show#editDescription" for element
Error: Bad action descriptor "click->card-show#editDescription": r.forOptions is not a function
at Function.e.forElementWithInlineDescriptorString (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:2)
at e.buildActionForElementWithDescriptorString (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:3)
at e.getConnectedActionForElementWithDescriptorString (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:3)
at e.elementUnmatchedTokenForAttribute (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:3)
at e.elementUnmatchedToken (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:3)
at e.elementUnmatched (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:3)
at e.removeElement (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:3)
at e.processNode (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:3)
at e.processRemovedNodes (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:2)
at e.processMutation (app-14f4dbd96b765d1f3cea6ce9a38b92d7.js?vsn=d:2)
What to do? 😄 ❓
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Fail To Start in Weblogic And Encounter Error Parsing ...
Fail To Start in Weblogic And Encounter Error Parsing Descriptor in Web Application After Patching (Doc ID 2465373.1)
Read more >WebLogic Error: Parsing failure in config.xml - Stack Overflow
I was able to resolve this by setting my DMW_HOME VM argument to my Middleware home directory. For example: -DMV_HOME="<your middleware home ...
Read more >Blazor wasm: Uncaught (in promise) Error: System ... - GitHub
Blazor wasm: Uncaught (in promise) Error: System.InvalidOperationException: There was an error parsing the event arguments. EventId: '13'.
Read more >WebLogic Exception error parsing descriptor in Web ...
If you use WebLogic to deploy a war project, some projects can be deployed, but some cannot. The following exception occurs.
Read more >Configuring a registry - Docker Documentation
The Registry configuration is based on a YAML file, detailed below. While it comes with sane default values out of the box, you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
just to clarify in case this happens to anyone, just add the following to your brunch config
@javan Thank you for pointing me in the right direction. It works now.