![]() Would have to test a failing build with a fork of 2.3 and revert macros back to. It was updated as a result of updating the package.json. This issue states the problem happened in this repo on version 2.3 Looking at the yarn lock of 2.3 we included. 41 of macros (and not sure why it didnt start being an issue til. The second link thinks that the error actually happened with. Please see FortAwesome/ember-fontawesome#194 and embroider-build/embroider#1077 ![]() It shows different error messages but it is the same error. You are receiving this because you commented.Message ID: … Triage notifications on the go with GitHub Mobile for iOS or Android. Reply to this email directly, view it on GitHub, or unsubscribe. To: miragejs/ember-cli-mirage Gantzler, Brian Comment Re: causing builds to fail > v2.2 (Issue #2343)Įxternal Email – Please use caution before opening attachments or clicking linksīuild Error (broccoli-persistent-filter:Babel > [Babel: in placeholder "APP": Expected string substitutionĪt populatePlaceholders Object.buildLiterals Object.inlineRuntimeConfig PluginPass.enter newFn Object.buildLiterals Object.inlineRuntimeConfig PluginPass.enter newFn NodePath._call NodePath.call NodePath.visit □31)Īt TraversalContext.visitQueue `node -trace-warnings. I had thought it was a font-awesome problems.Ĭould be another embroider migration problem.įeel a lot of addons are probably encountering these mirgration issuesįrom: PJ Carly Thursday, Februat 6:32 AM Interestingly I get that same error when I try to update ember font-awesome and staying on ember-cli-mirage 2.4. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:349084) DeprecationWarning: Unhandled promise rejections are deprecated. To terminate the node process on unhandled promise rejection, use the CLI flag `-unhandled-rejections=strict` (see ). This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with. (node:349084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. (node:349084) UnhandledPromiseRejectionWarning: Error: placeholder "APP": Expected string substitutionĪt populatePlaceholders Object.buildLiterals Object.inlineRuntimeConfig PluginPass.enter newFn Object.buildLiterals Object.inlineRuntimeConfig PluginPass.enter newFn NodePath._call NodePath.call NodePath.visit TraversalContext.visitQueue `node -trace-warnings. Ultimately and unfortunately, issues is not in ember-cli-mirage but in older version of used in v2. I would to try as it upgrades and should be pretty stable (although you should update all the import paths remove in #2314).Īnother option is to use resolutions and enforce hesitant to bump to v1 in ember-cli-mirage as it's breaking change.Īnother option to move forward is to release stable v3 with and rollback #2297 in v2 (which is not great option as well IMO). Upgrading to 1.0.0 would be a breaking change as it would ultimately require Node.js 12+. ![]() The problem with bumping is that it requires Node.js 12+ and ember-cli-mirage v2 supports Node.js 10. I guess this resurface some issues that exist in older version ember-cli-mirage > v2.2 I tried reproducing the error in a standalone app but couldn't get it to crash.
0 Comments
Leave a Reply. |