let groupModule = angular.module('app.group',['btford.socket-io']);
I have included socket.js and /socket.io/socket.io.js as well. Still getting this error. Completed all the steps in ReadMe but still getting this error.
Github repo
I am trying to use angular-socket-io.
Related
My react application is working fine until I wanted to wrap it up and deploy it. The build via vite build is successful. However, when the built folder "dist" is deployed and served, it says Uncaught TypeError: e is not a constructor.
After hours of debug, I can confirm that it's the aws-sdk that is causing the issue. In particular, the following code:
const s3 = new S3({
accessKeyId: VITE_ACCESS_KEY_ID,
secretAccessKey: VITE_SECRET_ACCESS_KEY,
region: VITE_REGION,
});
I think the new S3(...config) here corresponds to a line that reads o = new e; in the compiled index.bad38efb.js file that gives the Uncaught TypeError: e is not a constructor error.
Ultimately the question comes down to, is there any alternative that I could authenticate with s3 or does anyone know how to resolve this problem? Please let me know what extra information could I provide to answer the question.
Had the same issue, although harder to debug since I was not getting any errors in building.
Solution is to move to the v3 version of the SDK which is better maintained (and has other benefits too).
Any time I import Amplify into my React Native project's App.js file, I get the following error:
TypeError: null is not an object (evaluating 'keys.filter')
Here is how I'm importing it:
I run the project using Expo only. If I comment the import Amplify line out, any other files which use anything related to Amplify cause the same error to occur.
Initially, when I was loading this project for the first time, I had other errors to deal with like first needing to create the aws-exports.js file. I copied this over from an old project (Because this is meant to be a re-do of another project that's already set up). Once I included that file I had to update a few lines in that file because of an improper reference to Linking from expo. Once I fixed that, it throw this error I'm referencing here. Now, even if I delete the aws-exports file it will throw this error as soon as Amplify is imported into the App.js file.
-- Update
I've found where the error is occurring. Some of my code gets executed but the error happens inside of the reactnative.js file when syncing between two memory software.
I've tried to reproduce this error inside a fresh react application by copying the package.js file and then importing Amplify into the App.js file but it doesn't throw this error.
Here is a screenshot of where the error is taking place. I'm still trying to figure out how to pinpoint where in my code this error begins.
According to Expo, you have to follow these steps
it would be best if you imported Amplify
import Amplify from '#aws-amplify/core'
All you need to follow those steps it sees the configuration issue result data is not coming that's why it gives a null value and crashes.
Follow steps below will fix your problem
https://blog.expo.dev/how-to-build-cloud-powered-mobile-apps-with-expo-aws-amplify-2fddc898f9a2
The problem seems to be resolved by changing the slug attribute in the react app.json file. I changed the slug from being a camel case to an all lower case slug.
After this the error has gone away for what seems permanent. I've been able to replicate the error in small sample apps. I don't understand why this causes these errors.
I got this error but I have no idea why I got this error. I did everything fine. I am using useRecoilState in Next JS to manage my state.
Here's the link to repo: https://github.com/dingus45191/Radiant-Covid-Emergency-Site
Works now just remove any unnecessary recoil imports
I downloaded your project, build it, ran it with npm start, the app loads fine. See below,
I do get an error in the console, but I believe that is irrevalent with your error. See below.
We are trying to upgrade our react project to latest packages including relay (7.0.0). Our application builds and works but we are getting this error message in the console (during build) on every file where we import graphql from 'babel-plugin-relay/macro'. We are doing exactly like documented here adding relay
The error is "There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information." It is coming from \node_modules\babel-plugin-macros\dist\index.js in getConfig( ).
To understand how other projects were configured, I downloaded another sample relay project / installed it and it had the same problem. Interesting enough there was this recent post in that app's issues list error loading config
The solution noted worked for me (adding that noted .babel-plugin-macrosrc.yml file with empty relay plugin?) but I am not understanding why this is needed or what was causing this seemingly benign error message?
I've been working with my repo for a while, it's a clone of the angular2-seed repo. It includes webpack 2 (I think it's still beta) and async routes.
I did some tests and reverted to a previous state, but after installing packages with npm it fails loading async components with the following message in the browser:
browser_adapter.js:85 EXCEPTION: Error: Uncaught (in promise): Error: Cannot find module './+tickets'.
The plus sign is not a typo, the folder is actually called "+tickets" and it contains an index.ts file. It always worked, and now for some reason it doesn't.
I tried everything, but the error is so clueless that I don't know where to watch. Maybe the webpack-dev-server is not serving the files correctly..?
An alternative plan would be to start everything from scratch and then move the modules, but I'm really interested to where the problem is for future implementations.
Thanks a lot for the help
Hi I've created Angular2 lazy loading demo using RC 6.
Please checkout https://github.com/Quramy/ng2-lazy-load-demo .