You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. First step
When using commitlint, I have used a conventional commit
2. Second step
Unable to commit due to the current behaviour
Current Behavior
Seeing the below error message
import { findUp } from ‘find-up’;
^^^^^^
SyntaxError: Named export ‘findUp’ not found. The requested module ‘find-up’ is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from ‘find-up’;
const { findUp } = pkg;
Expected Behavior
I should be able to commit correctly
Affected packages
cli
core
prompt
config-angular
Possible Solution
I have added Find Up as a dependancy
"dependencies": {
"find-up": "^7.0.0"
}
Context
I would like to be able to remove this dependancy as it's a direct dependancy of the Commit Lint package, not required by my application
commitlint --version
@commitlint/cli": "^19.5.0"
git --version
git version 2.47.1
node --version
v20.9.0
The text was updated successfully, but these errors were encountered:
Steps to Reproduce
Current Behavior
Seeing the below error message
import { findUp } from ‘find-up’;
^^^^^^
SyntaxError: Named export ‘findUp’ not found. The requested module ‘find-up’ is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from ‘find-up’;
const { findUp } = pkg;
Expected Behavior
I should be able to commit correctly
Affected packages
Possible Solution
I have added Find Up as a dependancy
"dependencies": {
"find-up": "^7.0.0"
}
Context
I would like to be able to remove this dependancy as it's a direct dependancy of the Commit Lint package, not required by my application
commitlint --version
@commitlint/cli": "^19.5.0"
git --version
git version 2.47.1
node --version
v20.9.0
The text was updated successfully, but these errors were encountered: