I have recently upgraded a .net Core (2.1) / Angular 6 SPA app to the latest versions. I seemed to have done everything correctly at one point, but I made a change that broke the http (port 5000) app. I get an error:
vendor.js:1 Uncaught ReferenceError: module is not defined
at vendor.js:1
This is the first line of the vendor.js file. When I run the app using port 5001 (https), everything seems to work fine. I cannot figure out why there is a difference in the two websites as they are hitting the same code base.
To begin this upgrade, I started with the official dotnet core 2.1 Angular SPA and upgrade angular from 5 to 6.
I had this exact error and fixed it by changing the port number for the App URL in the Project Properties.
Hope this helps, however I'm still not sure what caused the issue.
Related
I have recently upgraded my EE magento 2.2.6 to 2.3.2. The category pages are are showing error on front-end:
Exception #0 (DomainException): Undefined factory mysql
Also some of my cms pages showing error (possibly due to newly added functionality of Pagebuilder (turning it off doesn't resolve the issue) by Magento):
Argument 2 passed to Magento\PageBuilder\Plugin\Filter\TemplatePlugin::afterFilter() must be of the type string, null given, called in /vendor/magento/framework/Interception/Interceptor.php on line 146
Anyone??
Resolved: For part 1: It was some configuration issue, so I downloaded the core_config_data table and replaced it with my staging site one
For part 2: I was using VladmirPopov webforms extension, it was causing the issue in cms pages, so downloaded the latest version of webforms extension and replaced it.
I use feathers for some months now and I already created and used several services. The app is generated with feather/cli command: 'feathers generate app'.
Today I tried to generate a new service with the usual command:
feathers generate service
only to get the error:
× This version of the generator will only work with Feathers Buzzard (v3) and up. Please runfeathers upgradefirst.
Fine. Run the upgrade. Got new error:
throw new Error('It looks like#feathersjs/feathersis already a dependency. I can not run the upgrade again.');
^
checked the version: is 3.9.0
Uninstalled/re-installed feathers/cli
Nothing works. Not sure what I broke as I did not (remember to) upgrade anything since a couple of days ago when I created the last service. Feathers was not updated in the last 4 months.
I tried googling my error but it seems like nobody else has this problem so it has to be something I've done.
Any suggestions?
LE: I have in package.json dependencies:
"#feathersjs/errors": "^3.3.6",
"#feathersjs/express": "^1.3.1",
"#feathersjs/feathers": "^3.3.1",
"#feathersjs/socketio": "^3.2.9",
"feathers-knex": "^5.0.7",
"feathers-memory": "^3.0.2",
"feathers-rest": "^1.8.1",
"feathers": "^2.2.4",```
This error will be shown if you still have the feathers module in your dependencies in your package.json. If #feathersjs/feathers is already included as well you can just remove the feathers dependency (after making sure it is not used anywhere else in your application which it shouldn't).
I am getting the usual error:
ERROR in Error: Metadata version mismatch for module C:/.../node_modules/#ng-bootstrap/ng-bootstrap/index.d.ts, found version
4, expected 3, resolving symbol AppModule in C:/.../app.module.ts, ...
I have looked at other posts on here with regards to version differences in the package.json file, however I am unsure which is causing the issue.
You can see from the github page that bootstrap expects angular version 5.0.2 and you are using 4.2.4. So probably upgrading to angular 5 will solve your issue.
https://github.com/ng-bootstrap/ng-bootstrap/blob/master/package.json
We have an Xcode Server bot set up for CI for our project, using Xcode 7.1. It's set to produce an IPA. We only recently noticed, but a few weeks ago, it started giving this warning every build:
Bot Issue for CareConsult Bot (develop) (build service warning)
Assertion: exportArchive: ipatool failed with an exception:
File: (null):(null)
This prevents it from producing an IPA, which is a problem.
I've tried:
- Creating a new bot
- updating gems (saw a similar issue that was resolved this way)
Doing an archive & export on my local machine gives the same error if I choose to "Export for specific device". So the problem is not specific to the build server.
Any ideas?
My suspicion is that this has to do with enabling bit code, and the build bot is using the "compile from bitcode" option by default. I'm still digging into this, but figured I'd share what I have found thus far.
I have a web server with MONO 2.10.2 (fast-cgi) on a CentOS 6 box. Running a plain-vanilla MVC 3 site works great. However, when I add MySql.Data, it gives me a not-so-helpful error:
System.IO.FileLoadException: The assembly name is invalid.
My DLLs are in the right place. They're referenced properly. Everything has been done correctly, but Mono still complains that it can't find an assembly without telling me which one. The problem occurs after simply adding a reference to MySql.Data and without changing any code. I've looked through the MySql.Data source solution and the references that it needs seem to exist on the web server.
I understand other people have the same problem. I am happy to debug it myself, but I'm new to Mono and I can't figure out how to get a more-detailed error messages. I've checked Mono's site for instructions to enable more detailed logging, but their docs assume a certain base knowledge about Mono that I do not have.
Is there a way to get more detailed information when Mono fails to load an assembly?
I'm not sure if these details matter, but just in case...
- Mono: 2.10.2 (served via fastcgi-mono-server4)
- MySql: Connector.Net 6.4.4.0 (from the v4 set in the .Net & Mono download)
- Webserver: NGINX 1.0.11
- OS: CentOS 6
If you can get a "test case" that compiles to an application, try:
MONO_LOG_LEVEL="debug" MONO_LOG_MASK="dll" mono my_app.exe
Or just temporarily edit your CGI script so that it sets those two variables. Check the logs - you should see what is not loaded propely.