You don't to install docker and all the other components of SigNoz to develop frontend. Follow the below steps for a much simpler process. We have hosted SigNoz on an ec2 instance and exposed the URL of the query-service which is the only thing that frontend needs to work. Steps for Frontend Contribution 1.

git clone <https://github.com/SigNoz/signoz.git> && cd signoz/frontend

2. change baseURL to 

<http://ec2-18-191-251-86.us-east-2.compute.amazonaws.com:8080>

 in file 

src/constants/env.ts

3. yarn install 4. yarn dev UI should show up at http://localhost:3000

@User @User Can we grab the value baseUrl in File from .env if the value is undefined we could set it to empty string

is anyone getting this error ?

Would be good to follow https://www.conventionalcommits.org/en/v1.0.0/ for uniformity?

just tried to build the docker image …to run at

3000

port and container exited with this log

2021/07/11 07:24:47 [emerg] 1#1: host not found in upstream "signoz-query-service" in /etc/nginx/conf.d/default.conf:20
nginx: [emerg] host not found in upstream "signoz-query-service" in /etc/nginx/conf.d/default.conf:20

How to address the problem we had in PR 212 where build image check is passing but the UI does not render and throws an error on console? Did any of you use UI functional testing tools earlier?

https://github.com/SigNoz/signoz/pull/224 ( Made a PR for that issue If anyone free pls do review and give me Feed back )

<!channel> Please try to fill in the above doc with whatever structure you seem fit or read somewhere. We can iterate by commenting in the doc. Let's try to fix on best practices by next weekend and we can start working on a part of it. Also, would it be okay to have a frontend specific call next weekend to finalise on the doc? @User @User @User @User would be great to have your inputs on this.

Hi All, right now there are some of the pointers that are boggling over my mind while seeing the codebase. Please feel free to point out if there are anything wrong or suggestions to improve. 1. There are improvements in how we structure the components (as we are spending initial pr review in that only and that can be improved hence minimised) 2. leveraging the typescript (as there are some places where typescript errors are there)

@User @User @User, @User, @User why do we have both

package-lock.json

and

yarn.lock

files even though we're using

yarn

, should I remove

package-lock

file

@User we already removed

package.lock.json

in this PR

<!channel> Welcoming @User into our community 🎉 🚀. He has recently joined SigNoz and now works as a full-time maintainer of SigNoz frontend.

Hi everyone. Can someone help me with the Test Env Url for using with the frontend as mentioned in the Contributing guidelines

@User have integrated the eslinting , tools on PR, testing coverage tools? sonarqube?

@User @User @User Can we extract out the frontend repo. REasons: 1. its confusing within same repo 2. in github also it act as single repo with backend, 3. issues on github combined in same issues as like single repo.

Hi everyone! I am looking for a test-env-url. I am working on a frontend-specific issue.

Hello guys can any one look into this one https://github.com/SigNoz/signoz/issues/313

Hello all, glad to be here. I am Bhavin and I am contributing to this issue here and wanted some help resolving this. I haven't actually worked on

Cypress

before. Since the issue says that

Cypress

expect shouldn't break, can someone help me on how can I run and verify cypress tests locally? Thanks!

👋 Hello, team!

Hello all! I am Estee from 🇸🇬. Will be helping out on this issue on migrating the webpack config from js to ts 🙂 Happy hacktoberfest everyone!

Hello Guys. is there a way can test Chart.js via any testing mechanism (e2e,unit... etc) found one use case to test via screenshot (don't know whether this is right approach or not ) probably by this we can guess whether the canvas is rendering or not (by mocking the response)

Congrats @User on having your first PR merged in SigNoz 🎉 🙂 - https://github.com/SigNoz/signoz/pull/334

Hello team ! I am Kinshuk I have worked on frontend technologies like React, Typescript,Jest looking forward to contribute and learn amazing things !

Hi Everyone,I'm Nagaraj & developed some good personal projects on MERN & looking forward in contributing frontend part of signoz.can someone share test environment url?

Hello Everyone! I am Astha Nayak, a undergraduate student of National Institute of Technology Rourkela. I am interested in contributing towards the SigNoz project. I am basically into frontend and application development but I would be more than happy to contribute in any way possible. Cheers 💖

Hello Everyone, I am Yogesh Saraogi currently started working in DevOps. I am interested in contributing to the #365 issue in the SigNoz project. Maintainer, please help me to start on this. Thank you

I am getting this error $ NODE_OPTIONS="--loader ts-node/esm" NODE_ENV=development webpack serve --config=webpack.config.ts --progress 'NODE_OPTIONS' is not recognized as an internal or external command, operable program or batch file. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. I have added .env file inside frontend folder. classic.yarnpkg.com Yarn Fast, reliable, and secure dependency management. @User

$ yarn dev yarn run v1.22.17 $ NODE_OPTIONS="--loader ts-node/esm" NODE_ENV=development webpack serve --config=webpack.config.ts --progress { args: [ 'NODE_OPTIONS=--loader', 'ts-node/esm', 'NODE_ENV=development', 'webpack', 'serve', '--config=webpack.config.ts', '--progress' ], env: { NODE_OPTIONS: '--loader' }, cmd: [ 'ts-node/esm', 'NODE_ENV=development', 'webpack', 'serve', '--config=webpack.config.ts', '--progress' ] } C:\Program Files\nodejs\node.exe: --loader requires an argument Note: This command was run via npm module 'win-node-env' error Command failed with exit code 9.

Hi new here and pretty new to open source, I’m Faith and I’m a React developer. I’m looking around, I’ll ask when I need it, thanks! 🙂