identity-obj-proxy | An identity object using ES6 proxies Useful for mocking webpack imports like CSS Modules | Script Programming library

This may be a silly answer. Try checking whether the task is running or any other programs interfereing the app, like an antivirus.

No. What Webpack ends up including is not something published or reported. Using react-scripts alone would seen hundreds of modules and versions being shipped in production. Any library you add on top just adds to that weight.

With tree shaking and build deps, you can't rely upon that requires at all. Some of those, like Jest or ESLint, are dev-only. They have no runtime. Others will. Some runtime deps will be shaken out too, so can't rely on just recognizing the lib.

In this case you should move '\\.(scss|sass|css)$': 'identity-obj-proxy' to the top entry of your moduleNameMapper object. As the ordering matters, your .scss file import is being matched against '^@project(.*)$' first.

gatsby-plugin-sharp, according to the documentation:

• @babel/runtime
• async
• bluebird
• filenamify
• fs-extra
• gatsby-core-utils
• gatsby-telemetry
• got
• imagemin
• imagemin-mozjpeg
• imagemin-pngquant
• lodash
• mini-svg-data-uri
• potrace
• prob-image-size
• progress
• semver
• sharp
• svgo
• uuid
• Dev dependencies: @babel/cli, @babel/core, @types/sharp, babel-preset-gatsby-package, cross-env, gatsby-plugin-image, gatsby-plugin-utils

On the other side, mozjpeg has:

• bin-build
• bin-wrapper
• logalot
• Dev dependencies: ava, bin-check, compare-size, execa, tempy, xo

I'm a bit surprised you're loading types from the types.d file direct and with a build path! I'd expect rather import { Type } from '@myorg/component-library.

That's because as part of creating the package.json for a typescript-authored npm library you'd be defining a main property pointing to the place that exports all the Javascript properties and a types property pointing to the place that exports the typescript types you want.

If that main entry point (because of your build process) is actually build/index.js and the corresponding types file is build/index.d.ts then you'd never directly reference the build folder or files when importing - pointing to the right path is dealt with by the bundling process.

Take a look at a mainstream (but simple) typescript npm module like https://github.com/jamiebuilds/unstated-next/blob/master/package.json ( https://www.npmjs.com/package/unstated-next )

You can see the main property pointing to the file which should export the javascript names https://github.com/jamiebuilds/unstated-next/blob/master/package.json#L6 and the types property pointing to the file which should export the types https://github.com/jamiebuilds/unstated-next/blob/master/package.json#L9 and these happen to be in the 'dist' folder but this is never referenced when importing it as per the docs at https://www.npmjs.com/package/unstated-next

I downgraded the sqlite3 package to v5.0.0 and it rebuilt correctly. Hope this helps anyone else with the same issue.

Source: nodejs electronjs sqlite3 - use of undeclared identifier 'napi_is_detached_arraybuffer'

Your code looks fine but:

Looks like your test file is a js file (src\__tests__\DatePicker.spec.js) instead of ts?x file which means this pattern will never meet "^.+\\.(ts|tsx)$": "ts-jest".

However, you might know tsc can also have capability to transpile your js code as well as long as you set allowJs: true as you already did. So I think your problem would be fixed as you refine your pattern to to transform above including jsx file:

ESLint reports config errors as an issue with the first line of files it's applied to. As @sleepwalker mentioned it should have to do with your eslint config (e.g. .eslingrc).

Looking up the first rule that is failing: no-empty-label.

It has the following warning:

This rule was removed in ESLint v2.0 and replaced by the no-labels rule.

So it's likely you need to follow the error recommendations, and make those modifications to your ESLint config.

Example: