I am trying to copy this sandbox. I copied everything and installed Konva, use-image and react-konva, but I got 2 errors. The first is that canvas is missing so I installed that. After the installation,I got this error:
Error [ERR_REQUIRE_ESM]: require() of ES Module C:\User\Folder\node_modules\konva\lib\Core.js from C:\User\Folder\node_modules\react-konva\lib\ReactKonvaCore.js not supported.
I am using Next13.
The error itself happens in a weird sense. If I navigate to the page from any link it works, but if I refresh the page, I get the errors.
Related
I am upgrading my static site from Nuxt3-RC3 to Nuxt3-RC11.
After upgrading I get a lot of errors and warnings in the console related to my dynamic routes (/m/[...slug].vue). It appears, that Nuxt is trying to prefect the dynamic pages it finds links to (e.g. /m/some/page) by looking up an _payload.js for each dynamic route. The warning is, that
ERROR: Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.
WARNING: entry.8994fad8.js:5 [nuxt] Cannot load payload /m/d6746dd9-497b-4f9a-8201-513b19762ccd/f6358aa0-07a4-46c4-b3eb-9d6c515f07c7/_payload.js TypeError: Failed to fetch dynamically imported module: /m/d6746dd9-497b-4f9a-8201-513b19762ccd/f6358aa0-07a4-46c4-b3eb-9d6c515f07c7/_payload.js
(anonymous) # entry.8994fad8.js:5
When I click to open the _payload.js in the browser file I can see, that it is rendered as an html file which explains the mime type error.
But, why is Nuxt throwing these errors and warnings and how can I avoid them?
This is no longer a problem. Solution is to upgrade to the new stable Nuxt3
I am attempting to install Font Awesome Pro in my NextJS app, which is deployed via Vercel. However, I keep getting this error:
error An unexpected error occurred: "https://npm.fontawesome.com/#fortawesome/pro-light-svg-icons/-/5.15.4/pro-light-svg-icons-5.15.4.tgz: Request failed \"401 Unauthorized\""
Then the build exits with Error: Command "yarn install" exited with 1
Locally everything works great. I have the following in my .npmrc file:
#fortawesome:registry=https://npm.fontawesome.com/
//npm.fontawesome.com/:_authToken=NPM_RC
And then within Vercel settings I have an environmental variable with the name NPM_RC and the value is my personal Pro-Token.
As an aside: I tried doing a global setup using my token but that returns the same error mentioned above. When I reached out to Font Awesome they said that Global setups can be hit or miss and that I should try the .npmrc route.
I reached out to Font Awesome after giving the .npmrc route and try and still having the error. They are not sure what is going on... I am stuck and any help would be greatly appreciated. Cheers!
I needed to update my .npmrc file with the following:
#fortawesome:registry=https://npm.fontawesome.com/
//npm.fontawesome.com/:_authToken=${NPM_RC}
Thank you #robmadole!
I've been trying to create a local copy of this wordpress site - click4taps.co.uk. But even though everything seems to run pretty much fine on the server, on localhost I am getting these code errors, I would have maybe expected a database error if I had forgot something in the setup. I'm not super good at php but I can't see anything that out of place in the code the error specifies.
Here is the error message I receive when trying to launch the site in localhost:
Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'woocommerce_layered_nav_init' not found or invalid function name in C:\Program Files (x86)\Ampps\www\click4taps\wp-includes\plugin.php on line 406
Fatal error: Call to undefined function is_product() in C:\Program Files (x86)\Ampps\www\click4taps\wp-content\themes\bazar\theme\plugins\woocommerce-ajax-layered-nav\init.php on line 59
Any feedback on this would be very helpful thanks
Activate your woocommerce plugin
I've just noticed that all of my checkboxes and radio buttons are missing labels on my drupal site admin menus. Not sure when this started (I've checked several backups, and it is present in all of them), but I'd like to find a solution.
I have tried disabling modules, but to no effect at the moment.
I've attached a screenshot
I have noticed a couple of PHP warnings pop up on a couple of pages - these are:
Warning: preg_match(): Compilation failed: unknown option bit(s) set at offset 0 in /persistent/html/includes/bootstrap.inc on line 1606
and
Warning: in drupal_clean_css_id![enter image description here][1]entifier() (line 3731 of /persistent/html/includes/common.inc).
Warning: preg_match(): Compilation failed: unknown option bit(s) set at offset 0 in /persistent/html/includes/bootstrap.inc on line 1606
was the clue apparently.
PHP had recently been upgraded from 5.3.13 to 5.3.14, and this seemed to change the way in which preg_match is handled. Upgraded again to 5.3.15 and the problem was still there - so I downgraded to 5.3.13 and the problem was solved.
Found other instances of people getting a similar preg_match error on Wordpress which subversion php upgrades!
I created a new static library in my iOS project and now I'm getting the build error
Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/libtool failed with exit code 1
How do I go about debugging this?
To see the actual output and not just the error message, try building your target or scheme with xcodebuild from command line.
I had a problem with the same error message. In my case, I couldn't build for the simulator, but it worked find when building for the device. The output from xcodebuild confirmed that Xcode could not set the proper architecture to build for the simulator.
Long story short, it turned out that one build setting was corrupted. The Mach-O Type setting in the Linking category was set to Relocatable Object File for some reason. I switched it back to Static Library and the error disappeared.