Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

options.test.js not found #190

Open
steinybot opened this issue Jan 28, 2021 · 1 comment · May be fixed by #191
Open

options.test.js not found #190

steinybot opened this issue Jan 28, 2021 · 1 comment · May be fixed by #191

Comments

@steinybot
Copy link

  • Operating System: macOS Big Sur 11.1
  • Node Version: v14.15.2
  • NPM Version: 6.14.9
  • webpack Version: 4.46.0
  • @webpack-contrib/defaults Version: 6.3.0

Expected Behavior

npm run defaults succeeds.

Actual Behavior

❯ npm run defaults

> remote-source-map-loader@1.0.0 defaults /Users/jason/source/webpack-remote-source-map-loader
> webpack-defaults

Synchronizing config files...
Create .gitignore
Create .gitattributes
Update package.json
Installing schema-utils and loader-utils...
+ schema-utils@3.0.0
+ loader-utils@2.0.0
added 8 packages from 11 contributors, updated 3 packages and audited 418 packages in 3.084s

10 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Installing del, del-cli, cross-env, memfs, standard-version, @commitlint/cli, @commitlint/config-conventional, commitlint-azure-pipelines-cli, husky, npm-run-all, jest, jest-junit, babel-jest, @babel/cli, @babel/core, @babel/preset-env, eslint, eslint-plugin-import, eslint-config-prettier, lint-staged, prettier, and @webpack-contrib/eslint-config-webpack...
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported

> husky@4.3.8 install /Users/jason/source/webpack-remote-source-map-loader/node_modules/husky
> node husky install

husky > Setting up git hooks
husky > Done

> core-js@3.8.3 postinstall /Users/jason/source/webpack-remote-source-map-loader/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)


> husky@4.3.8 postinstall /Users/jason/source/webpack-remote-source-map-loader/node_modules/husky
> opencollective-postinstall || exit 0

Thank you for using husky!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/husky/donate

npm WARN commitlint-azure-pipelines-cli@1.0.3 requires a peer of @commitlint/cli@^7.0.0 || ^8.0.0 but none is installed. You must install peer dependencies yourself.

+ del@6.0.0
+ cross-env@7.0.3
+ commitlint-azure-pipelines-cli@1.0.3
+ memfs@3.2.0
+ npm-run-all@4.1.5
+ del-cli@3.0.1
+ husky@4.3.8
+ jest@26.6.3
+ babel-jest@26.6.3
+ jest-junit@12.0.0
+ @babel/core@7.12.10
+ @babel/preset-env@7.12.11
+ eslint@7.18.0
+ eslint-plugin-import@2.22.1
+ eslint-config-prettier@7.2.0
+ lint-staged@10.5.3
+ prettier@2.2.1
+ @webpack-contrib/eslint-config-webpack@3.0.0
+ standard-version@9.1.0
+ @babel/cli@7.12.10
+ @commitlint/cli@11.0.0
+ @commitlint/config-conventional@11.0.0
added 1130 packages from 420 contributors and audited 1550 packages in 51.756s

84 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Create .github/ISSUE_TEMPLATE/DOCS.md
Create .github/ISSUE_TEMPLATE/SUPPORT.md
Create .github/ISSUE_TEMPLATE.md
Create .github/CODEOWNERS
Create .github/PULL_REQUEST_TEMPLATE.md
Create .github/FUNDING.yml
Create .editorconfig
Create .eslintignore
Create .eslintrc.js
Create .prettierignore
Create .prettierrc.js
Create azure-pipelines.yml
Create babel.config.js
Create commitlint.config.js
Create husky.config.js
Create lint-staged.config.js
Update LICENSE
Create .github/CONTRIBUTING.md
Create .github/ISSUE_TEMPLATE/BUG.md
Create .github/ISSUE_TEMPLATE/FEATURE.md
Create .github/ISSUE_TEMPLATE/MODIFICATION.md
Create src/index.js
Create src/cjs.js
Create src/options.json
Create CHANGELOG.md

Done. Happy webpacking!

Create test/loader.test.js
(node:48883) UnhandledPromiseRejectionWarning: MrmError: copyFiles: source file not found: /Users/jason/source/webpack-remote-source-map-loader/node_modules/@webpack-contrib/defaults/templates/test/options.test.js
    at /Users/jason/source/webpack-remote-source-map-loader/node_modules/mrm-core/src/fs.js:32:10
    at Array.forEach (<anonymous>)
    at copyFiles (/Users/jason/source/webpack-remote-source-map-loader/node_modules/mrm-core/src/fs.js:29:21)
    at /Users/jason/source/webpack-remote-source-map-loader/node_modules/@webpack-contrib/defaults/dist/tasks/templates.js:26:7
(Use `node --trace-warnings ...` to show where the warning was created)
(node:48883) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:48883) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Code

N/A

How Do We Reproduce?

Run:

npm init
npm install @webpack-contrib/defaults --save-dev
npm install webpack@^4.3.0 --save-dev
node node_modules/@webpack-contrib/defaults/lib/post_install.js
npm run defaults
@steinybot
Copy link
Author

Seems like this was broken in 79861c1 as templates.js was not updated to reflect the names of the 2 new files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant