Open skylerknight opened 2 years ago
@skylerknight package.json
contains incorrect "main" and "export" fields. Next changes fix the issue:
"main": "./dist/index.js",
"exports": {
".": {
"default": "./dist/index.js"
}
},
Upd: Nope, gives ReferenceError: exports is not defined in ES module scope
There is type: "module"
and index.mjs
present but it's not usable at least because of required utils.mjs
uses apca-w3
that isn't present in dependencies
but indevDependencies
.
@NateBaldwinDesign It became broken after PR #166 had been merged
@elyulka Aha,thanks for the info
what's the best way around so far? Backing to 1.0.0-alpha.13 gives me this #175. I might be missing something about how to use the package
Problem is still there
Description
Unable to use package. Keep getting "Module not found" or "No exported member" errors.
I have tried both npm and yarn, with CRA and vite.
Steps to reproduce
Initiate a basic application:
npx create-react-app learn-leo
Install package
npm i @adobe/leonardo-contrast-colors
Import Leonardo Package:
import * as Leo from "@adobe/leonardo-contrast-colors"
Expected behavior
Expected to be able to import and use the leonardo package.
Screenshots
Leonardo package and version
@leonardo-contrast-colors version: ^1.0.0-alpha.16
Environment
Additional context
It appears that there may be something wrong with the exposed modules/files for export.
UPDATE: I've tested with Version
1.0.0-alpha.13
and I am no longer seeing this error. It must have something to do with the latest release.