Refactor scss handling out of webpack, instead use sass-dart to compile. Update package.json with new commands, refactor old commands ot mak to make usage more c more clear. Fix linting issues.

re: https://github.com/oslabs-beta/infernode/issues/180

Refactored form sections into separate components Added tabbed interface for basic vs advanced captures Unified button / header styling across pages Unified sidebar width across pages

Bumps loader-utils from 2.0.2 to 2.0.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

I updated the port number in index.ts to avoid conflicts with the use of port 3000. I also changed the webpack proxy target to match the change.

'fix #207'

Refactor scss handling out of webpack, instead use sass-dart to compile. Update package.json with new commands, refactor old commands ot mak to make usage more c more clear. Fix linting issues.

closes: https://github.com/oslabs-beta/infernode/issues/180

Change appController to not use a subshell when starting processes to ensure we get the PID of the actual node app. Add perfController, similar to dtraceController Update routers

Added pino for Node.JS logging and pino-http for Express.JS request logging.

In development mode logs are output to stdout (the console), otherwise (e.g. in production usage) logs are output to ./infernode.log.

pino-http is now in use for all Express.JS requests. Non-error (2xx/3xx status codes) requests are logged at debug level and only output in development mode.

console.log has been partially swapped out for a pino logger object/method in low-churn areas of the codebase. Functions under active development can make the change when appropriate.

To use pino's logging functionality, simply import the object ( import logger from './utils/logging'; ) and then use one of the following methods depending on what is being logged. Time-stamping and printing the log level are automatically handled by pino.

logger.trace('This is the lowest level of logging, and wont appear unless pino is configured to show trace logs');
logger.debug('This level is appropriate for messages that should be shown during development but hidden in production');
logger.info('This level is appropriate for informational messages, such as what port a server is listening on');
logger.warn('This level is appropriate for non-critical errors (e.g. execution should continue, but there is a problem');
logger.error('This level is appropriate for critical errors (e.g. the application will or should halt execution');

Added back-end logic and functionality for the following: icicle charts can now be created differential flamegraphs can now be created if the user chooses two existing flamegraphs to compare generating icicle charts with either a dtrace or perf upload

still working on adding the standalone dtrace capture process, and node kill process.

The following endpoints are either setup or under construction:

/api/app/start --> start node app /api/app/stop --> stop node app

these dtrace captures will run with time given by user, having a separate stop button is a stretch stretch feature /api/dtrace/icicle --> runs dtrace and produces a icicle chart /api/dtrace/flamegraph --> runs dtrace and produces a flamegraph

/api/dtrace/run/icicle --> starts node app and runs dtrace all at once, generates icicle chart /api/dtrace/run/flamegraph --> starts node app and runs dtrace all at once, generates flamegraph

/api/captures/icicle --> generate icicle chart with given perf capture /api/captures/flamegraph --> generate flamegraph with given perf capture

/api/diff --> generate a differential flamegraph from two existing flamegraphs chosen by the client

Right now, if something goes wrong when running the exec child process then we don't have a way to retrieve the error code from the node process. Adding the ability to retrieve and check this code will help us identify issues going forward. It will also be valuable when we start sanitizing the user uploaded files.

Enforces ESLint passing for both client and server projects when PRing to dev or main.

Extends documentation on dev process including what GHA checks are performed, what npm run scripts are available, and how to use the Express.js global error handler.

Closes #34, closes #16.

Looks like this fails if a PR author does not have actions to the GHA secrets. Probably need to move this to a separate workflow that only triggers when a team member does the merge to dev/main, rather than just on PR filing.

Bumps loader-utils from 2.0.3 to 2.0.4.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Currently there is a mechanism in place to filter out the graphs by type so that the diff page only shows flamegraphs and ice graphs to compare. However it currently does not work.

when selecting graphs to compare on the differential page, if you have more than one page of flamegraphs, you can't compare graphs from different pages because the state that holds your selection is held locally instead of in redux

Currently the example apps are not included in the final npm package distributable, that should be fixed. We should also test them to make sure they work without installing additional dependencies (e.g. eliminating the express dependency from example-server.js). And finally we should add documentation and/or ui elements that allow easy usage of the example apps with infernode.

infernode vs infernode vs INFERNOde flame graph vs flamegraph / ice graph vs icegraph (BGregg uses both interchangeably) Node.JS vs Node.js vs Nodejs Express.JS vs Express.js vs Express