Tag: “react”: “^16.12.0”

Electron & React-BoilerPlate white screen

Post author By Full Stack
Post date July 21, 2020
No Comments on Electron & React-BoilerPlate white screen

I have this app that works perfectly fine in Dev mode but not in Production. My folder structure are (build,dist,node_modules,public,src). build dist node_modules public Main.js index.html src index.tsx In my package.json { "name": "test", "version": "0.8.0", "description": "test welness", "author": "Remote Buddy Inc.", "homepage": "./", "main": "public/Main.js", "dependencies": { "@aspnet/signalr": "^1.1.4", "@craco/craco": "^5.6.2", "abp-web-resources": "^5.1.1", […]

Tags __dirname); mainWindow.webContents.openDevTools(); mainWindow.on('closed', '../build/index.html')}` ) console.log('Let it go', 'public'), "!**/dist/**", "!**/node_modules/**" ], "@craco/craco": "^5.6.2", "@types/jest": "^24.0.23", "@types/moment-timezone": "^0.5.12", "@types/moment": "^2.13.0", "@types/node": "^12.12.14", "@types/react-document-title": "^2.0.3", "@types/react-dom": "16.9.4", "@types/react-loadable": "^5.5.2", "@types/react-router-dom": "^5.1.3", "@types/react": "^16.9.13", "@types/recharts": "^1.8.3", "abp-web-resources": "^5.1.1", "antd": "^3.26.0", "author": "Remote Buddy Inc.", "axios": "^0.19.2", "botframework-webchat": "^4.9.0", "browserslist": { "production": [ ">0.2%", "build": "craco build", "build": { "appId": "nonExistentID", "classnames": "^2.2.6", "copy-webpack-plugin": "^5.0.5", "craco-antd": "^1.14.1", "dependencies": { "@aspnet/signalr": "^1.1.4", "description": "test welness", "devDependencies": { "@types/classnames": "^2.2.9", "development": [ "last 1 chrome version", "directories": { "buildResources": "assets" }, "dist": "electron-builder" }, "eject": "react-scripts eject" }, "electron-builder": "^22.7.0" }, "electron-is-dev": "^1.2.0", "electron": "^9.1.0", "electron": "electron .", "extends": null }, "famfamfam-flags": "^1.0.0", "files": [ "build/**/*", "last 1 firefox version", "last 1 safari version" ] } } My public/Main.js const electron = require('electron'); const app = electron.app; const BrowserWindow =, "lodash": "^4.17.15", "main": "public/Main.js", "mobx-react": "^6.1.4", "mobx": "^5.15.0", "moment-timezone": "^0.5.31", "moment": "2.24.0", "not dead", "not op_mini all" ], "preelectron-pack": "yarn run build", "public/Main.js", "query-string": "^6.9.0", "react-document-title": "^2.0.3", "react-dom": "^16.12.0", "react-icons": "^3.10.0", "react-infinite-scroll-component": "^5.0.4", "react-infinite-scroller": "^1.2.4", "react-loadable": "^5.5.0", "react-moment": "^0.9.7", "react-numpad": "^5.1.1", "react-onclickout": "^2.0.8", "react-player": "^1.15.3", "react-router-dom": "^5.1.2" }, "react-scripts": "3.2.0" }, "react-star-ratings": "^2.3.0", "react-tiny-link": "^3.3.1", "react-youtube": "^7.11.2", "react": "^16.12.0", "recharts": "^1.8.5", "scripts": { "start": "craco start", "test": "craco test", "ts-import-plugin": "^1.6.1", "typescript": "^3.7.2" }, "universal-cookie": "^4.0.3" }, "version": "0.8.0", "win": { "target": [ "nsis" ] }, function () { mainWindow = null }) } app.on('ready', height = 800, HomePage, I have this app that works perfectly fine in Dev mode but not in Production. My folder structure are (build, package.json, src). build dist node_modules public Main.js index.html src index.tsx In my package.json { "name": "test", webPreferences: { nodeIntegration: false, webSecurity: false } }); mainWindow.loadURL( isDev ? 'http://localhost:3000' : `file://${path.join(__

Mastering Development

React hooks widget works when used directly but not when imported from NPM

Post author By Full Stack
Post date April 12, 2020
No Comments on React hooks widget works when used directly but not when imported from NPM

I have a moderately simple example of a React Hooks widget whose function it is to provide context hooks to provide state that can set a few strings and switch the current Material UI theme. Here is the working demo. By clicking on the button labeled “NEXT THEME” you can see the page toggle between […]

Tags 'format': 'es' }, 'node_modules/prop-types/index.js': [ 'elementType' ] } }), 'node_modules/react-is/index.js': [ 'ForwardRef', "@babel/plugin-transform-runtime": "^7.9.0", "@babel/preset-env": "^7.9.0", "@babel/preset-react": "7.0.0", "@babel/runtime": "^7.9.2", "@material-ui/core": "^4.9.8", "@material-ui/icons": "^4.9.1", "@material-ui/styles": "^4.9.6", "@rollup/plugin-json": "^4.0.2", "author": "sellis42", "cross-env": "^5.2.0", "description": "Code from CodeSandbox", "engines": { "node": "8" }, "jsnext:main": "dist/index.es.js", "main": "dist/index.js", "module": "dist/index.es.js", "npm": ">=5" }, "peerDependencies": { "react": "^16.12.0", "predeploy": "cd example && npm install && npm run build" }, "prepare": "npm run build", "publishConfig": { "access": "public", "react-dom": "^16.12.0", "react-scripts": "3.4.0", "react": "^16.12.0", "rollup-plugin-babel": "^4.4.0", "rollup-plugin-commonjs": "^9.3.4", "rollup-plugin-node-resolve": "^4.2.4", "rollup-plugin-peer-deps-external": "^2.2.2", "rollup-plugin-terser": "^4.0.4", "rollup": "^1.32.1", "scripts": { "build": "rollup -c", "sourceMap": true, "start": "rollup -c -w", "typeface-roboto": "0.0.75" } } I feel as if there is something missing from my rollup configuration. This project is on my local developm, "version": "0.0.1", (devDependencies) "@babel/core": "^7.9.0", { file: pkg.module, { useContext, {useEffect, {useState, // url({ exclude: ['**/*.svg'] }), along with some text changes indicating the name of the theme. Its a contrived example, and an example folder that demonstrates how to use the widget. I use npm link so that the example widget can use it, and I suspect that there is an issue with the way that I am rolling all this code up for publishing to NPM. I am using Rollup--here is rollup, and that is where I see the issue I'm trying to resolve. I can copy the entire root widget to a subfolder of the example src and import it fr, babel({ exclude: 'node_modules/**', browser: true, but the color will not change. The theme is provided by Material UI, but the idea is that at the top of my site, commonjs({ include: 'node_modules/**', format: 'cjs', I have a moderately simple example of a React Hooks widget whose function it is to provide context hooks to provide state that can set a few, I'm wrapping all content with context providers so that any nested widget can access shared state. Looks like this: import React from "react, it mostly works except for one import piece--the theme color will not change. All other state changes work right--all of the other state chan, json() ] }; And here is my package.json: { "name": "@data-factory/theme-context-test", memo, namedExports: { 'node_modules/react/index.js': [ 'createContext', output: [ { file: pkg.main, plugins: [ external(), resolve({ preferBuiltins: true, runtimeHelpers: true }), terser()

Mastering Development

How to make npm start work on a cloned React repository?

Post author By Full Stack
Post date March 22, 2020
No Comments on How to make npm start work on a cloned React repository?

I have created a new github repository with files from a working project I downloaded from another github repository of mine. I have run npm install. When I try npm start, I get the following error: npm ERR! missing script: start npm ERR! A complete log of this run can be found in: npm ERR! […]

Tags 'start' package.json file. This is what mine looks like: { "name": "myproject", "browserslist": { "production": [ ">0.2%", "dependencies": { "bootstrap-4-grid": "^3.2.0", "development": [ "last 1 chrome version", "eject": "react-scripts eject" }, "eslintConfig": { "extends": "react-app" }, "formik": "^2.1.4", "last 1 firefox version", "last 1 safari version" ] } } I have tried changing the start script to "start": "index.js" or "start": "App.js" as they're my main fi, "not dead", "not op_mini all" ], "private": true, "react-dom": "^16.12.0", "react-router-dom": "^5.1.2" }, "react-scripts": "3.2.0" }, "react-spring": "^8.0.27" }, "react": "^16.12.0", "scripts": { "start": "react-scripts start", "test": "react-scripts test", "use-places-autocomplete": "^0.5.4", "version": "0.1.0", "yup": "^0.28.1" }, //supposedly problematic "build": "react-scripts build", I get the following error: npm ERR! missing script: start npm ERR! A complete log of this run can be found in: npm ERR! /home/mycompute, I have created a new github repository with files from a working project I downloaded from another github repository of mine. I have run npm, this repository will be shared with other people -- will they have the same problem when they clone from my repository?

Mastering Development

Caused by: java.lang.Exception: Command `config` unrecognized

Post author By Full Stack
Post date March 14, 2020
No Comments on Caused by: java.lang.Exception: Command `config` unrecognized

After Running Copied React-native project: Caused by: java.lang.Exception: Command config unrecognized. Make sure that you have run npm install and that you are inside a react-native project. I did npm install but it didn’t help. Package.json { “name”: “ProjectName”, “version”: “0.0.1”, “private”: true, “scripts”: { “android”: “react-native run-android”, “ios”: “react-native run-ios”, “start”: “react-native start”, “test”: […]

Tags "@babel/runtime": "7.8.4", "@philly25/react-native-paytm": "^1.0.12", "@react-native-community/datetimepicker": "^2.2.1", "@react-native-community/eslint-config": "0.0.5", "@react-native-community/google-signin": "^3.0.4", "@react-native-community/masked-view": "^0.1.6", "@react-native-community/netinfo": "^5.3.3", "@react-native-community/push-notification-ios": "^1.0.6", "babel-jest": "^25.1.0", "dependencies": { "@invertase/react-native-apple-authentication": "^0.1.1", "devDependencies": { "@babel/core": "7.8.4", "eslint": "^6.5.1", "fuse.js": "^3.4.6", "ios": "react-native run-ios", "jest": "^25.1.0", "jest": { "preset": "react-native", "lint": "eslint ." }, "lottie-react-native": "^3.3.2", "metro-react-native-babel-preset": "0.58.0", "moment": "2.24.0", "postinstall": "node ./scripts/stfu.js" }, "private": true, "react-native-action-button": "file:./custom_modules/react-native-action-button", "react-native-android-sms-listener": "^0.7.0", "react-native-calendar-picker": "file:./custom_modules/react-native-calendar-picker", "react-native-calendars": "file:./custom_modules/react-native-calendars", "react-native-carousel-view": "file:./custom_modules/react-native-carousel-view", "react-native-chart-kit": "file:./custom_modules/react-native-chart-kit", "react-native-fbsdk": "^1.1.2", "react-native-fetch-polyfill": "1.1.3", "react-native-firebase": "^5.6.0", "react-native-fs": "^2.16.2", "react-native-gesture-handler": "^1.5.6", "react-native-google-drive-api-wrapper": "^1.2.0", "react-native-google-fit": "^0.9.17", "react-native-google-signin": "^2.1.1", "react-native-image-pan-zoom": "^2.1.11", "react-native-image-picker": "^2.3.0", "react-native-modal-datetime-picker": "^8.1.3", "react-native-modal": "^11.5.3", "react-native-options-menu": "^2.0.2", "react-native-otp-input": "file:./custom_modules/react-native-otp-input", "react-native-popup-menu": "^0.15.7", "react-native-push-notification": "^3.1.9", "react-native-raw-bottom-sheet": "^2.0.6", "react-native-reanimated": "^1.7.0", "react-native-render-html": "^4.2.0", "react-native-responsive-dimensions": "^3.0.0", "react-native-restart": "0.0.13", "react-native-safe-area-context": "^0.6.4", "react-native-screens": "^2.0.0-beta.1", "react-native-select-input-ios": "file:./custom_modules/react-native-select-input-ios", "react-native-simple-toast": "^1.0.0", "react-native-size-matters": "^0.3.0", "react-native-slideable-calendar-strip": "file:./custom_modules/react-native-slideable-calendar-strip", "react-native-snap-carousel": "^3.8.4", "react-native-svg": "^11.0.1", "react-native-swipe-gestures": "^1.0.4", "react-native-swipe-list-view": "^2.1.3", "react-native-tag-select": "file:./custom_modules/react-native-tag-select", "react-native-vector-icons": "6.6.0", "react-native-webview": "^8.0.6", "react-native": "0.61.5", "react-navigation-stack": "^2.1.0", "react-navigation-tabs": "^2.7.0", "react-navigation": "^4.1.1", "react-test-renderer": "^16.12.0", "react": "^16.12.0", "realm": "^4.0.0-beta.0" }, "rnpm": { "assets": [ "./app/res/fonts/" ] } }, "scripts": { "android": "react-native run-android", "start": "react-native start", "test": "jest", "version": "0.0.1", After Running Copied React-native project: Caused by: java.lang.Exception: Command config unrecognized. Make sure that you have run npm inst

Mastering Development

Error rendering react-redux functional component when data is deleted from firestore (useFirestoreConnect)

Post author By Full Stack
Post date March 9, 2020
No Comments on Error rendering react-redux functional component when data is deleted from firestore (useFirestoreConnect)

My ArticleList component is successfully getting & displaying the user’s list of articles from firestore when I first load the app. The user can click a “Remove Article” button, which successfully removes the article from the subcollection in firestore, but it causes an error in the rendering of the react component, which seems to still […]

Tags "firebase": "^7.5.2", "isomorphic-fetch": "^2.2.1", "materialize-css": "1.0.0-rc.2", "prop-types": "15.7.2", "react-dom": "^16.12.0", "react-redux-firebase": "^3.0.5", "react-redux": "^7.1.3", "react-router-dom": "^5.1.2" }, "react": "^16.12.0", "redux-firestore": "^0.11.0", "redux-thunk": "^2.2.0", "redux": "3.7.2", "style-loader": "^1.0.1", "styled-jsx": "^3.2.4", "uuid": "3.3.3" }, [firestore] ); ...then the return statement maps through myArticles such that each article is displayed as a list item with a button that in, [myArticles]); Here are the package versions: "dependencies": { "css-loader": "^3.2.1", ArticleId, but I decided to post my question first in case I can just use hooks in this component. No other components/parts of the app need access to t, but I'm still learning how to use react hooks and therefore struggling a bit. Beginning of the ArticleList component: const ArticleList = (, but it causes an error in the rendering of the react component, but no success: const [myArticlesState, doc: userId, err); }); }; } I've tried adding useState and useEffect in the ArticleList as follows (and tried having the component's return statement m, getState) => { const userId = getState().firebase.auth.uid; firestore .collection('users') .doc(userId) .collection('articles') .doc(, I'd like to keep this a functional component and use hooks rather than making it a class, id }); }) .catch(err => { console.log('Error: ', id) => { return (dispatch, id); dispatch({ type: 'REMOVE_ARTICLE', My ArticleList component is successfully getting & displaying the user's list of articles from firestore when I first load the app. The user, Note: I do not currently have this article list in overall app state/redux store/props at all. This is something I was thinking of trying nex, setMyArticlesState] = useState(myArticles); useEffect(() => { setMyArticlesState(myArticles); }, storeAs: userId + '::articles' } ]); const myArticles = useSelector(state => state.firestore.data[`${userId}::articles`]); const dispatch = u, subcollections: [{collection: 'articles'}], which seems to still be trying to render the article that was just removed and is now null. Is there something else I can do to make my react, which successfully removes the article from the subcollection in firestore

Development

Jest encountered an unexpected token – React with jest and enzyme

Post author By Full Stack
Post date March 6, 2020
No Comments on Jest encountered an unexpected token – React with jest and enzyme

tsconfig.json { “extends”: “./node_modules/pcf-scripts/tsconfig_base.json”, “compilerOptions”: { “typeRoots”: [“node_modules/@types”], “allowJs”: true, “skipLibCheck”: true, “esModuleInterop”: true, “allowSyntheticDefaultImports”: true, “forceConsistentCasingInFileNames”: true, “module”: “esnext”, “moduleResolution”: “node”, “resolveJsonModule”: true, “isolatedModules”: true, “sourceMap”: true }, “include”: [“./ConsumptionSummaryComponent/src”, “ConsumptionSummaryComponent/globals.d.ts”], “exclude”: [“./node_modules/pcf-scripts/./node_modules”] } .babelrc file { “env”: { “test”: { “plugins”: [ “@babel/plugin-transform-modules-commonjs” ] } } } Package.json { “name”: “pcf-project”, “version”: “1.0.0”, […]

Tags '^.+\\.tsx?$': 'ts-jest' }, "^.*.svg$": "/src/blank-mock.js" }, "^.+\\.jsx$": "ts-jest" }, "^style-loader.*$": "/ConsumptionSummaryComponent/src/blank-mock", "@babel/preset-env": "^7.8.4", "@common-pcf/sdk": "file:../sdk/common-pcf-sdk-1.0.0.tgz", "@graphql-codegen/introspection": "1.12.1", "@graphql-codegen/typescript-operations": "1.12.1", "@graphql-codegen/typescript-react-apollo": "1.12.1", "@graphql-codegen/typescript": "1.12.1", "@microsoft/applicationinsights-web": "^2.3.1", "@types/enzyme-adapter-react-16": "1.0.6", "@types/enzyme": "3.10.5", "@types/jest": "^25.1.1", "@types/node": "^10.12.18", "@types/powerapps-component-framework": "^1.2.0", "@types/react-dom": "^16.9.5", "@types/react": "^16.9.19", "@uifabric/fluent-theme/lib/": "@uifabric/fluent-theme/lib-commonjs/", "@uifabric/icons": "^7.3.2", "@uifabric/styling/lib/": "@uifabric/styling/lib-commonjs/", "/ConsumptionSummaryComponent/src/services/**/*.{ts, "/js/**", "allowJs": true, "allowSyntheticDefaultImports": true, "apollo-boost": "^0.4.7", "babel-jest": "^25.1.0", "babelConfig": "/ConsumptionSummaryComponent/.babelrc", "clean": "pcf-scripts clean", "collectCoverage": true, "collectCoverageFrom": [ "/ConsumptionSummaryComponent/src/components/**/*.{ts, "compilerOptions": { "typeRoots": ["node_modules/@types"], "ConsumptionSummaryComponent/globals.d.ts"], "coverageDirectory": "test-coverage", "coverageReporters": ["lcov"], "coverageThreshold": { "global": { "branches": 0, "cra-template-typescript": "^1.0.0", "dependencies": { "@apollo/react-hooks": "^3.1.3", "description": "Project containing your PowerApps Component Framework (PCF) control.", "devDependencies": { "@babel/core": "7.8.4", "diagnostics": { "ignoreCodes": [ "TS1149" ] } } }, "enzyme-adapter-react-16": "^1.15.2", "enzyme-to-json": "3.4.4", "enzyme": "^3.11.0", "esModuleInterop": true, "exclude": ["./node_modules/pcf-scripts/./node_modules"] } .babelrc file { "env": { "test": { "plugins": [ "@ba, "expose-loader\\?jQuery\\!jquery": "/ConsumptionSummaryComponent/src/blank-mock", "forceConsistentCasingInFileNames": true, "functions": 0, "globals": { "ts-jest": { "tsConfig": "tsconfig.json", "graphql-tag": "^2.10.2", "graphql": "^14.6.0", "include": ["./ConsumptionSummaryComponent/src", "isolatedModules": true, "jest": "^25.1.0", "jest": { "roots": [ "/ConsumptionSummaryComponent/src" ], "lines": 0 } }, "module": "esnext", "moduleFileExtensions": [ "ts", "moduleNameMapper": { "ts-jest": "/node_modules/ts-jest", "moduleResolution": "node", "office-ui-fabric-react": "^7.84.0", "office-ui-fabric-react/lib/": "office-ui-fabric-react/lib-commonjs/", "pcf-scripts": "^1", "pcf-start": "^1", "react-dom": "^16.12.0", "react": "^16.12.0", "rebuild": "pcf-scripts rebuild", "resolveJsonModule": true, "scripts": { "build": "pcf-scripts build", "setupFiles": [ "/ConsumptionSummaryComponent/src/setupEnzyme.ts" ], "skipLibCheck": true, "source-map-loader": "^0.2.4", "sourceMap": true, "start": "pcf-scripts start", "statements": 0 } }, "test:watch": "jest --watch" }, "test": "jest", "transform": { "^.+\\.js$": "/node_modules/babel-jest", "ts-jest": "25.1.0", "ts-loader": "^6.2.1" } } SetupEnzyme.ts import { configure } from 'enzyme'; import Adapter from 'enzyme-adapter-react-16'; configure({, "version": "1.0.0", "webpack-cli": "^3.3.10", "webpack": "^4.41.5" } }, () => { const result = shallow(); expect(result).toMatchSnapshot(); }); Error Jest encountered an, e.g. it's not plain JavaScript. By default, iconName: Enums.ProductTypeLogo.azureLogo, iconStyle: styles.AzureIcon, if Jest sees a Babel config, ignoring "node_modules". Here's what you can do: • To have some of your "node_modules" files transformed, isEnabled:true, it will use that to transform your files, json, jsx, node, order: 1 }; it("Should render the Summary component for the test Product Group Summary", productGroupName: Enums.ProductTypeName.azureProductTypeName, snapshotSerializers: ['enzyme-to-json/serializer'], testEnvironment: 'node', testRegex: '(/__tests__/.*|(\\.|/)(test|spec))\\.tsx?$', ts=x, tsconfig.json { "extends": "./node_modules/pcf-scripts/tsconfig_base.json", you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in you

Development

I cannot configure my package.js file for ReactJS

Post author By Full Stack
Post date February 28, 2020
No Comments on I cannot configure my package.js file for ReactJS

This is the error: Insufficient number of arguments or no entry found. Alternatively, run ‘webpack(-cli) –help’ for usage info. And this is the code in my package.json file: { “name”: “reactredux”, “version”: “1.0.0”, “description”: “React”, “main”: “index.js”, “scripts”: { “start”: “npm run build”, “build”: “webpack -d && copy src/index.html dist/index.html && webpack-dev-server –content-base src/ –inline […]

Tags "author": "NikolaMilicevic", "babel-preset-es2015": "^6.24.1", "babel-preset-react": "^6.24.1", "babel-preset-stage-2": "^6.24.1", "build:prod": "webpack -p && copy src/index.html dist/index.html" }, "build": "webpack -d && copy src/index.html dist/index.html && webpack-dev-server --content-base src/ --inline --hot", "dependencies": { "babel-loader": "^8.0.6", "description": "React", "devDependencies": { "webpack-cli": "^3.3.11" } }, "keywords": [ "react" ], "license": "MIT", "main": "index.js", "react-dom": "^16.12.0", "react": "^16.12.0", "scripts": { "start": "npm run build", "version": "1.0.0", "webpack-dev-server": "^3.10.3" }, "webpack": "^4.41.6" }, run 'webpack(-cli) --help' for usage info. And this is the code in my package.json file: { "name": "reactredux", This is the error: Insufficient number of arguments or no entry found. Alternatively

Development

Eslint config error. ESLint couldn’t find the config “dev” to extend from

Post author By Full Stack
Post date February 28, 2020
No Comments on Eslint config error. ESLint couldn’t find the config “dev” to extend from

I’m trying to set up eslint to TS react project, but run into err: > eslint . Oops! Something went wrong! 🙁 ESLint: 6.8.0. ESLint couldn’t find the config “dev” to extend from. Please check that the name of the config is correct. The config “dev” was referenced from the config file in “C:\Users\User\Desktop\priority-style-react\example\node_modules\@csstools\convert-colors\package.json”. If […]

Tags '@typescript-eslint', 'description': None, "@babel/plugin-proposal-class-properties": "^7.8.3", "@babel/preset-env": "^7.8.4", "@babel/preset-react": "^7.8.3", "@babel/preset-typescript": "^7.8.3", "@svgr/rollup": "^2.4.1", "author": "iLavs", "babel-loader": "^8.0.6", "babel-plugin-import": "^1.12.0", "babel-plugin-require-context-hook": "^1.0.0", "babel-runtime": "^6.26.0", "build": "rollup -c", "cross-env": "^5.2.1", "declaration-bundler-webpack-plugin": "^1.0.3", "dependencies": { "classnames": "^2.2.6" }, "devDependencies": { "@babel/core": "7.8.4", "ecmaVersion": 2018, "engines": { "node": "8" }, "es6": true }, "eslint-config-airbnb": "^18.0.1", "eslint-plugin-jsx-a11y": "^6.2.3", "eslint-plugin-react-hooks": "^1.7.0", "eslint-plugin-react": "^7.18.3", "eslint": "6.8.0", "files": [ "dist/*" ], "globals": { "Atomics": "readonly", "jsnext:main": "dist/index.es.js", "license": "MIT", "main": "dist/index.js", "markdown-loader": "^5.1.0", "mini-css-extract-plugin": "^0.7.0", "module": "dist/index.es.js", "npm": ">=5" }, "parserOptions": { "ecmaFeatures": { "jsx": true }, "peerDependencies": { "prop-types": "15.x", "plugins": [ "react" ], "postcss-loader": "^2.1.6", "prettier": "^1.19.1", "react-dom": "^15.0.0 || ^16.0.0" }, "react": "^15.0.0 || ^16.0.0", "react": "^16.12.0", "repository": "", "rollup-plugin-babel": "^4.3.3", "rollup-plugin-commonjs": "^10.1.0", "rollup-plugin-node-resolve": "^5.2.0", "rollup-plugin-peer-deps-external": "^2.2.0", "rollup-plugin-postcss": "^2.0.3", "rollup-plugin-typescript2": "^0.25.2", "rollup-plugin-url": "^3.0.0", "rollup": "^1.27.1", "sass-loader": "^7.1.0", "scripts": { "lint": "eslint .", "SharedArrayBuffer": "readonly", "sourceType": "module", "start": "rollup -c -w", "style" ] } my .eslintrc.js: module.exports = { env: { browser: true, "ts-loader-decleration": "^0.10.4", "ts-loader": "^2.3.7", "typescript": "^3.7.2" }, "url-loader": "^2.0.1" }, “eslint-plugin-import”: “^2.20.1”, ], { "Version", }, $rules, Airbnb, awesome-typescript-loader : ^5.2.1, but run into err: > eslint . Oops! Something went wrong! :( ESLint: 6.8.0. ESLint couldn't find the config "dev" to extend from. Please c, can someone help me?, extends: [ 'plugin:react/recommended', fonts, I'm trying to set up eslint to TS react project, parser: '@typescript-eslint/parser', please stop by https://gitter.im/eslint/eslint to chat with the team. my package.json looks like: { "name": "######"

Development

Heroku Deployment Continues to Fail at “Pruning devDependencies” Step

Post author By Full Stack
Post date February 17, 2020
No Comments on Heroku Deployment Continues to Fail at “Pruning devDependencies” Step

I continue to have issues deploying to Heroku and I can’t find out what is going wrong for the life of me. The Heroku error log tells me this after it successfully builds my react app: —–> Caching build – node_modules —–> Pruning devDependencies npm ERR! Cannot read property ‘match’ of undefined Here is my […]

Tags "author": "John Doe", "axios": "^0.19.0", "bcryptjs": "^2.4.3", "body-parser": "^1.18.3", "browserslist": { "production": [ ">0.2%", "build": "cd client && react-scripts build", "classnames": "^2.2.6", "client-install": "npm install --prefix client", "client": "npm start --prefix client", "concurrently": "^5.1.0", "date-fns": "^2.8.1", "debug": "^4.1.1", "depcheck": "^0.9.1", "dependencies": { "@material-ui/core": "^4.8.0", "description": "test", "dev": "concurrently \"npm run server\" \"npm run client\"", "devDependencies": {}, "development": [ "last 1 chrome version", "engines": { "node": "12.x" }, "eslint-plugin-flowtype": "^4.6.0", "express": "^4.16.4", "fibers": "^4.0.2", "growl": "^1.10.5", "heroku": "^7.35.1", "history": "^4.10.1", "is-empty": "^1.2.0", "jquery": "^3.4.1", "jsonwebtoken": "^8.3.0", "jwt-decode": "^2.2.0", "last 1 firefox version", "last 1 safari version" ] } } What is perhaps most frustrating, "license": "MIT", "main": "server.js", "material-table": "^1.54.2", "material-ui": "^0.20.2", "minimatch": "^3.0.4", "moment": "^2.23.0", "mongodb": "^3.5.3", "mongoose-global": "^1.0.1", "mongoose": "^5.8.9", "morgan": "^1.9.1", "node-sass": "^4.13.0", "node": "v12.13.1", "not dead", "not op_mini all" ], "npm": "6.13.7", "passport-jwt": "^4.0.0", "passport": "^0.4.0", "plaid": "^4.6.0", "react-dom": "^16.12.0", "react-ga": "^2.7.0", "react-plaid-link-button": "0.0.4", "react-router-dom": "^5.1.2" }, "react-scripts": "3.3.0" }, "react-slick": "^0.25.2", "react-stripe-elements": "^6.0.1", "react-vis": "^1.11.7", "react": "^16.12.0", "redux-thunk": "^2.3.0" }, "sass": "^1.24.0" } }, "scripts": { "heroku": "node server.js", "server": "nodemon server.js" }, "slick-carousel": "^1.8.1", "slick": "^1.12.2", "start": "node server.js", "typescript": "^3.7.4", "update-mongo": "0.0.4", "validator": "^12.2.0", "version": "1.0.0", "vis": "^4.21.0-EOL" }, HomePage, I continue to have issues deploying to Heroku and I can't find out what is going wrong for the life of me. The Heroku error log tells me this, is that I was able to deploy successfully once the other day but I am not sure what changed. Going back through my git I can't see anything t

Development

Axios post request fails to use proxy

Post author By Full Stack
Post date February 16, 2020
No Comments on Axios post request fails to use proxy

I’m currently testing out the endpoints on my server via a React client using Axios. I have a proxy (http://localhost:8080) set up in my package.JSON for my client. All my GET requests are successful. My POST requests on the other-hand all fail to make use of the proxy provided in package.JSON, instead, it’s using (http://localhost:3000). […]

Tags ...)' instead., "@testing-library/react": "^9.4.0", "@testing-library/user-event": "^7.2.1", "axios": "^0.19.2", "browserslist": { "production": [ ">0.2%", "build": "react-scripts build", "dependencies": { "@testing-library/jest-dom": "^4.2.4", "development": [ "last 1 chrome version", "eject": "react-scripts eject" }, "eslintConfig": { "extends": "react-app" }, "last 1 firefox version", "last 1 safari version" ] } } Any ideas as to how I can remedy this? Thanks for any and all suggestions., "not dead", "not op_mini all" ], "private": true, "proxy": "http://localhost:8080", "react-dom": "^16.12.0", "react-router-dom": "^5.1.2" }, "react-scripts": "3.3.1" }, "react": "^16.12.0", "scripts": { "start": "react-scripts start", "test": "react-scripts test", "version": "0.1.0", data); }, email:email}, I'm currently testing out the endpoints on my server via a React client using Axios. I have a proxy (http://localhost:8080) set up in my pack, it's using (http://localhost:3000). Please see code below Login Component function Login{ const handleSubmit = (e) =>{, password:password}) .then((res) => console.log(res)) .catch((err) => console.log(err)); } return(, port: "8080" } }) console.log(res); } catch(err){ console.log(err), proxy:{ host: "localhost", url: "/user/login"