Tag: “allowJs”: true

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

Why is this React Typescript app throwing errors?

Post author By Full Stack
Post date February 8, 2020
No Comments on Why is this React Typescript app throwing errors?

I just created a new React app using npx create-react-app my-app –template typescript and it was working fine until I changed my component to from a stateless one to a stateful one. The error: JSX element type ‘App’ is not a constructor function for JSX elements. TS2605 3 | import App from “./App”; 4 | […]

Tags "@testing-library/react": "^9.3.2", "@testing-library/user-event": "^7.1.2", "@types/jest": "^24.0.0", "@types/node": "^12.12.26", "@types/react-dom": "^16.9.0", "@types/react": "^16.9.19", "@types/styled-components": "^4.4.2", "allowJs": true, "allowSyntheticDefaultImports": true, "browserslist": { "production": [ ">0.2%", "build": "react-scripts build", "dependencies": { "@testing-library/jest-dom": "^4.2.4", "development": [ "last 1 chrome version", "dom.iterable", "eject": "react-scripts eject" }, "eslintConfig": { "extends": "react-app" }, "esModuleInterop": true, "esnext" ], "forceConsistentCasingInFileNames": true, "include": ["src"] } Update after trying @Vlad's answer below: Changed import * as React from "react" to import React from "react" and now, "isolatedModules": true, "jsx": "react" }, "last 1 firefox version", "last 1 safari version" ] } } tsconfig.json { "compilerOptions": { "target": "es5", "lib": [ "dom", "module": "esnext", "moduleResolution": "node", "not dead", "not op_mini all" ], "private": true, "react-dom": "^16.12.0", "react-scripts": "3.3.0" }, "react": "^16.12.0", "resolveJsonModule": true, "scripts": { "start": "react-scripts start", "skipLibCheck": true, "strict": true, "styled-components": "^5.0.0", "test": "react-scripts test", "types": ["node"] }, "typescript": "^3.7.5" }, "version": "0.1.0", ) ); } // setState(() { //, //"noEmit": true, and 2 more. TS2605 3 | import App from "./App"; 4 | > 5 | ReactDOM.render(, document.getElementById("root")); | ^ 6 |, document.getElementById("root")); All the solution I could find suggested supplying props and state to the class as well as upgrading to the, error: null }; } handleChange = (event: any) => { console.log("changing", event); }; handleSubmit = (event: any) => { event.preventDefault(); console.log("submitting", event); }; render() { return ( <input typ, forceUpdate, I just created a new React app using npx create-react-app my-app --template typescript and it was working fine until I changed my component t, props, State> { constructor(props: Props) { super(props); this.state = { zipCode: ""

Development

How to stop TypeScript error ‘Type A has no properties in common with Type B’ when Type B “extends” Type A in some way

(edited Title to make more general) I’m working in a codebase which uses React class components and Typescript everywhere, and I’m trying to implement react-dropzone (a lightweight, simple but effective file-drop component) using the class-based method. The Hooks implementation is cleaner and simpler but I’d prefer to avoid so as to preserve the paradigm maintained […]

Tags 'build'), 'webpack'] }, "acceptance-tests", "allowJs": true, "Dom", "esModuleInterop": true, "experimentalDecorators": true, "forceConsistentCasingInFileNames": true, "jsx": "react" }, "lib": ["es6", "module": "esnext", "moduleResolution": "node", "noImplicitAny": true, "noImplicitReturns": true, "noImplicitThis": true, "noUnusedLocals": true, "noUnusedParameters": true, "scripts/*.js", "sourceMap": true, "src/setupTests.ts" ] } Also here's a complete example: import React from "react"; import { observable, "strict": true, "strictNullChecks": true, "suppressImplicitAnyIndexErrors": true, "target": "es5", (edited Title to make more general) I'm working in a codebase which uses React class components and Typescript everywhere, { DropzoneState } from "react-dropzone"; //... export class BasicDropzone extends React.Component { onDrop = (files: Array) => {, { DropzoneState } from "react-dropzone"; const styles = require('./dropzone.css'); @observer export class BasicDropzone extends React.Compo, // See https://github.com/rexxars/react-markdown/issues/207 "allowSyntheticDefaultImports": true, // See https://stackoverflow.com/questions/52399839/typescript-duplicate-identifier-librarymanagedattributes // for the reason for this., action } from 'mobx'; import { observer } from 'mobx-react'; import Dropzone, and I'm trying to implement react-dropzone (a lightweight, baseUrl, exclude: /node_modules/, getInputProps}) => ( Drag 'n' drop some files, here are the Typescript definitions from the react-dropzone package of relevance: export type DropzoneState = DropzoneRef & { isFocused: b, HTMLInputElement>'. ts(2559) Just for further info, it uses plain Javascript. Here's a typical example: import React from 'react' import Dropzone from 'react-dropzone' <Dropzone onDrop={accep, Jest, or click to select files )} This seems a fairly unusual syntax anyway... I've discovered that, or click to select files Files, simple but effective file-drop component) using the class-based method. The Hooks implementation is cleaner and simpler but I'd prefer to avo, so I am trying to get it to work using the following: import Dropzone

Development

Protractor – MacOS – SyntaxError: Unexpected token ‘export’

Post author By Full Stack
Post date December 3, 2019
No Comments on Protractor – MacOS – SyntaxError: Unexpected token ‘export’

Hi everybody: I have some issues in Protractor. I’m new trying to config Protractor in Mac with VSCode (I couldn’t to that with Eclipse, it was really hard to do) I’m creating a project from the beginning with Protractor. I have created a conf.js file: export const config = { framework: ‘jasmine2’, specs: [‘specs/*.spec.js’], onPrepare: […]

Tags 'base64')); stream.end(); }); });, "@types/node": "^12.12.14", "allowJs": true, "author": "Rodrigo González", "babel-cli": "^6.26.0", "babel-core": "^6.26.3", "dependencies": { "@types/jasmine": "^3.5.0", "description": "Final Protractor Framework", "devDependencies": { "@babel/preset-env": "^7.7.4", "fs-extra": "^8.1.0", "jasmine-reporters": "^2.3.2" } } My babel file: newFunction() function newFunction() { { "presets"; ["@babel/preset-env"], "jasmine-spec-reporter": "~4.2.1", "jasmine": "^3.5.0", "license": "ISC", "main": "conf.js", "protractor-html-reporter-2": "^1.0.4", "protractor": "^5.4.2", "scripts": { "test": "echo \"Error: no test specified\" && exit 1", "ts-node": "^8.5.4", "typescript": "^3.7.2" }, "version": "1.0.0", browserVersion; var capsPromise = browser.getCapabilities(); capsPromise.then(function (caps) { browserName = c, browserVersion: browserVersion, filePrefix: 'guitest-xmloutput', function (err) { console.log(err); }); jasmine.getEnv().addReporter({ specDone: f, Hi everybody: I have some issues in Protractor. I'm new trying to config Protractor in Mac with VSCode (I couldn't to that with Eclipse, it was really hard to do) I'm creating a project from the beginning with Protractor. I have created a conf.js file: export const config = {, mixed mode, modifiedSuiteName: false, onComplete: function() { //Getting HTML report var browserName, onPrepare: function(){ // Getting CLI report const SpecReporter = require('jasmine-spec-reporter').SpecReporter; jasm, outputFilename: 'ProtractorTestReport', outputPath, savePath: '.' })); //Getting screenshots var fs = require('fs-extra'); fs.emptyDir('screenshots/', screenshotPath: './screenshots', screenshotsOnlyOnFailure: true, sharing) After run protractor conf.js I have the next issue: [14:53:01] E/configParser - Error code: 105 [14:53:01] E/configParser - Error, specs: ['specs/*.spec.js'], testBrowser: browserName, testConfig); }); } } This is my json file: { "name": "protractor_initium", testPlatform: platform }; new HTMLReport().from('guitest-xmloutput.xml'

Development

Report typescript errors as warnings in Visual Studio and don’t fail the build

Post author By Full Stack
Post date December 3, 2019
No Comments on Report typescript errors as warnings in Visual Studio and don’t fail the build

I want to typecheck existing javascript code. To that end, I have specified the following tsconfig. Running tsc results in a couple of hundred errors, which show up in Visual Studio when I do a build. However those errors now also fail the build. As the code is currently functioning, I want to postpone resolving […]

Tags "allowJs": true, "noEmit": true } } //csproj (abbreviated) <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVe, "noEmitOnError": true, "removeComments": false, "sourceMap": true, "target": "es5", 0 skipped ==========, 1 failed, 23 up-to-date, checkJs: true, I have specified the following tsconfig. Running tsc results in a couple of hundred errors, I want to postpone resolving those errors. I want the errors to be reported as warnings, I want to typecheck existing javascript code. To that end, such that the build will continue and we can gradually improve the javascript. // tsconfig.json { "compilerOptions": { "noImplicitAny", which show up in Visual Studio when I do a build. However those errors now also fail the build. As the code is currently functioning

Development

typescript cannot find module when import svg file

Post author By Full Stack
Post date November 6, 2019
No Comments on typescript cannot find module when import svg file

It’s web application created with Typescript, React and webpack. I want to use svg file through webpack. However, I got TS2307: Cannot find module ‘~/images/slide.svg’. Typescript files are put on /frontend/src/, and typescript files are build successfully. Then, I tried some solutions on website. But I could not solve this problem. What I tried is […]

Tags "./node_modules/@types" ], "**/*.js" ] } types/images.d.ts declare module '*.svg' { const content: any; export default content; } I use 'file-loader' on webpac, "allowJs": true, "allowSyntheticDefaultImports": true, "awesomeTypescriptLoaderOptions": { "useCache": true, "bundles", "cacheDirectory": "tmp/build_caches/awesome-typescript-loader" }, "include": [ "./frontend/src/*" ], "jsx": "react" }, "module": "es2015", "moduleResolution": "node", "noImplicitAny": true, "noUnusedLocals": true, "noUnusedParameters": true, "paths": { "~/*": ["./frontend/src/*"] }, "removeComments": true, "sourceMap": true, "target": "es6", "typeRoots": ["types", and typescript files are build successfully. Then, baseUrl, exclude: /node_modules/, I got TS2307: Cannot find module '~/images/slide.svg'. Typescript files are put on /frontend/src/, I tried some solutions on website. But I could not solve this problem. What I tried is described briefly as follows. I added a file where de, It's web application created with Typescript, React and webpack. I want to use svg file through webpack. However

Development

Typescript cannot find module defined in paths

Post author By Full Stack
Post date October 25, 2019
No Comments on Typescript cannot find module defined in paths

I have a typescript application that has paths for absolute imports. My tsconfig looks like this: { “compilerOptions”: { “baseUrl”: “.”, “paths”: { “utils*”: [“src/utils*”], “operations*”: [“src/operations*”], “actions*”: [“src/actions*”], “components*”: [“src/components*”], “constants*”: [“src/constants*”], }, “outDir”: “dist”, “module”: “esnext”, “target”: “esnext”, “moduleResolution”: “node”, “noEmit”: true, “lib”: [“es2017”, “dom”], “noUnusedLocals”: true, “sourceMap”: true, “skipLibCheck”: true, “allowJs”: true, […]

Tags "!**/dist/**", "actions*": ["src/actions*"], "allowJs": true, "allowSyntheticDefaultImports": true, "components/*": ["src/components/*"], "constants/*": ["src/constants/*"], "Dom", "files": [ "./typings/index.d.ts" ] } and I'm trying to use imports like so: import { AppStateType } from 'actions/app'; howev, "include": [ "src" ], "jsx": "preserve" }, "lib": ["es2017", "module": "esnext", "moduleResolution": "node", "noImplicitAny": true, "noUnusedLocals": true, "noUnusedParameters": true, "operations*": ["src/operations*"], "outDir": "dist", "paths": { "utils*": ["src/utils*"], "preserveConstEnums": true, "skipLibCheck": true, "sourceMap": true, "strict": true, "target": "esnext" }, ], }, //"noEmit": true, exclude: /node_modules/, I have a typescript application that has paths for absolute imports. My tsconfig looks like this: { "compilerOptions": { "baseUrl"

Development

Nuxt TypeScript error: nuxt:typescript Cannot find module ‘@/my-module’

Post author By Full Stack
Post date October 21, 2019
No Comments on Nuxt TypeScript error: nuxt:typescript Cannot find module ‘@/my-module’

I have setup Nuxt with TypeScript using the instructions from https://typescript.nuxt.org. The transition was pretty seamless and ok, except that I can’t get rid of this error that nuxt:typescript “Cannot find module”, which obviously is a false-positive. My imports look like this: import InputField from ‘@/components/InputField.vue’ I have tried with ~/ and without the .vue […]

Tags 'src'), "@nuxt/types"] }, "allowJs": true, "Dom", "esModuleInterop": true, "esnext.asynciterable", "exclude": ["node_modules"] } And I have this object in my nuxt.config.js: typescript: { typeCheck: { eslint: true, "lib": [ "esnext", "module": "esnext", "moduleResolution": "node", "paths": { "@/*": [ "src/*" ] }, "sourceMap": true, "strict": true, "types": ["@types/node", //"noEmit": true, baseUrl, except that I can't get rid of this error that nuxt:typescript "Cannot find module", I have setup Nuxt with TypeScript using the instructions from https://typescript.nuxt.org. The transition was pretty seamless and ok, vue: true } }, which obviously is a false-positive. My imports look like this: import InputField from '@/components/InputField.vue' I have tried with ~/

Development

“Navbar refers to a value, but is being used as a type here” when trying to render a shallow copy of my component when testing

I am trying to write a test to my React component, using TypeScript, Jest as my test runner and Enzyme for testing my React components. Whenever I pass my component into the shallow Enzyme function, I get the ts error “‘Navbar’ refers to a value, but is being used as a type here.”, and underneath […]

Tags "**/*.spec.ts", "**/*.test.ts"] } jest.config.ts: module.exports = { roots: ['/src'], "/js/**", "allowJs": true, "allowSyntheticDefaultImports": true, "dom.iterable", "ecmaFeatures": { "jsx": true } }, "esModuleInterop": true, "esnext" ], "forceConsistentCasingInFileNames": true, "include": [ "src" ], "isolatedModules": true, "jsx": "react" }, "lib": [ "dom", "module": "esnext", "moduleFileExtensions": [ "ts", "moduleResolution": "node", "parserOptions": { "ecmaVersion": 6, "resolveJsonModule": true, "skipLibCheck": true, "sourceType": "module", "strict": true, () => { expect(component).toMatchInlineSnapshot(); expect(component.length).toBe(1); expect(component).toBeTruthy();, () => { let component; beforeEach(() => { component = shallow(); // Error being desplayed here }); it('sho, }, }; Enzyme setup: import { configure } from 'enzyme'; import Adapter from 'enzyme-adapter-react-16'; import 'jest-enzyme'; configure({ adap, //"noEmit": true, all have the same error when being passed into the shallow function as arguments. I suspect it may have something to do with my TS configurat, and underneath I get eslint error "Parsing error: '>' expected". I tried it on some other components, but for the life of me I cannot seem to be finding a solution. Here's the code for Navbar.tsx: import React from 'react'; import { shallow, but is being used as a type here.", disableLifecycleMethods:, exclude: /node_modules/, I am trying to write a test to my React component, I get the ts error "'Navbar' refers to a value, Jest as my test runner and Enzyme for testing my React components. Whenever I pass my component into the shallow Enzyme function, json, jsx, node, setupTestFrameworkScriptFile: '/src/setupEnzyme.ts', snapshotSerializers: ['enzyme-to-json/serializer'], testRegex: '(/__tests__/.*|(\\.|/)(test|spec))\\.tsx?$', transform: { '^.+\\.tsx?$': 'ts-jest', ts=x, using TypeScript

Development

TypeScript: click event’s .target property fails to be found in EventTarget object

Post author By Full Stack
Post date October 12, 2019
No Comments on TypeScript: click event’s .target property fails to be found in EventTarget object

In the code below, TypeScript seems to be inspecting what I believe is a base class EventTarget but it can not find the target property. It was working in regular JS before I recently converted this project to TS, so clearly the target property must be there. The alternative is I’m typing this variable incorrectly. […]

Tags "allowJs": true, "include" : ["./templates/**/*"], "module": "commonjs", "sourceMap": true, "target": "es5", event: EventTarget) => { const clickedTabArray = tabArray.filter(tabId => tabId === event.target.id); // property 'target' doesn't exist on, event); }; document.addEventListener('click', exclude: /node_modules/, HTMLAnchorElement. None of these cleared the red lint (it did move to id for I think MouseEvent). const findClickedTab = (tabArray: object[], HTMLDivElement, in the code below, MouseEvent, so clearly the target property must be there. The alternative is I'm typing this variable incorrectly. Is that the case? Also tried Typing, switchSection); Update 1 Below is my tsconfig.json. I know it's at least partially incorrect because files/folders outside ./templates are, TypeScript seems to be inspecting what I believe is a base class EventTarget but it can not find the target property. It was working in regu, which attaches to the event listener const switchSection = event => { const tabIdsArrayOfStrings = getTabIds(); const clickedTabIdStri, which is parallel / a hierchical sibling of ./templates) { "compilerOptions" : { "outDir" : "./compiledJs"