Hi @brouk2426 Museo Sans license is restrected for use with Enact Application. Please refer to the full license at https://github.com/enactjs/moonstone/blob/master/fonts/MuseoSans/LICENSE.txt
@ericblade You can setup resolve aliases with Webpack, that should accomplish what you're looking for: https://webpack.js.org/configuration/resolve/
just updated to 4.1.6, doesn't seem to work there either
i should've called it relative paths, not absolute paths, i thought that sounded weird, but all the articles were like 'absolute paths are amazing'.. but these aren't absolute paths. sorry if that caused any confusion
2 hours to clone and figure out how to add the feature to enact, get it added to my production server, and touch every single file in my application to update for it. not too bad.
@ericblade ,
Thanks for the PRs. Enact CLI does support "resolve.alias" (https://webpack.js.org/configuration/resolve/#resolvealias) through package.json as "alias" property.
But I guess you wanted to resolve additional paths.
I understand what's the pain point for developers and I think it's reasonable to add the feature.
I found Create React App also supports the feature through js/tsconfig file. (https://create-react-app.dev/docs/importing-a-component/#absolute-imports)
Fortunately, we have plans for adopting Webpack5 near future, we'll take a look at how we could achieve this while updating Webpack.
I think "enact" object in package.json is a good start point. Thanks for the suggestion!
Thanks for the PRs. Enact CLI does support "resolve.alias" (https://webpack.js.org/configuration/resolve/#resolvealias) through package.json as "alias" property.
But I guess you wanted to resolve additional paths.
I understand what's the pain point for developers and I think it's reasonable to add the feature.
I found Create React App also supports the feature through js/tsconfig file. (https://create-react-app.dev/docs/importing-a-component/#absolute-imports)
Fortunately, we have plans for adopting Webpack5 near future, we'll take a look at how we could achieve this while updating Webpack.
I think "enact" object in package.json is a good start point. Thanks for the suggestion!
hmm. i just looked up those fields, and for the specific purpose, it does look like both can be used to achieve what i wanted, though it does look like there might be good reasons to have both.
If you'd like to accept that change, but need me to make any changes to it, just lmk. I'm not sure my choice of variable names fits well.
I've just discovered that having a component slide out on flick is a really interesting UI thing I want to toy with, but Android keeps getting in the way
onFlick={() => { do_thing_flick_should_do(); document.body.style.overscrollBehaviorY = 'auto'; }}
onTouchMove={(ev) => { document.body.style.overscrollBehaviorY = 'contain';}}
requires NODE_OPTIONS=--openssl-legacy-provider right now
it looks like this doesn't effect 16, this is a new change in 17. my production server uses 16 and doesn't set this, though i try to keep my dev machines up to date when i'm active on them. so, not a big deal, but someone will need to be aware that node 17+ will break npm run serve
Thank you, Eric. Sorry for the delay, I’m only seeing msgs at the office. You can just insert React components anywhere in the app, right? One other question, if you will: I’m having the most stupidest thing, where I try to insert an image using the Sandstone Image component, but it doesn’t render. Neither inside a panel, or inside a DIV. Any thoughts?