feat: Add ESM support for common and sdk-client. #1007
kinyoklionreact-native.yml
on: pull_request
build-test-react-native
57s
Annotations
10 errors
|
build-test-react-native
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './api/context/LDContextCommon.js'?
|
|
build-test-react-native
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
build-test-react-native
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AttributeReference.js'?
|
|
build-test-react-native
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
build-test-react-native
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './validators.js'?
|
|
build-test-react-native
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
build-test-react-native
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AttributeReference.js'?
|
|
build-test-react-native
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './Context.js'?
|
|
build-test-react-native
Binding element 'kind' implicitly has an 'any' type.
|
|
build-test-react-native
Binding element 'single' implicitly has an 'any' type.
|