npm installing from repo with #main #2470
-
|
I am banging my head on the wall here, I can't figure this out. I am missing something but can't figure out what. So here's how it starts. The repo has been update with #2223. So I want to benefit asap from the new code and I go ahead and do an On my dev env I start investigating:
I say, ok, it's a cache problem. I start and remove every cache I can think of possible. From the browser and from npm. Whatever I do, browser code (line 81) is still not updated to #2223 code At this point I'm thinking, ok, my env is messed up. I go make a fresh, vm, install windows on it and then:
I have literally no idea why, how, where it's fetching the old code from. Please help with anything 🙏 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hey @Dorian-Grim However, we don't regenerate what's inside I think that if you want to achieve that, you have to recompile the CSS file from the Scss files contained in |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for this!
I can now benefit from the |
Beta Was this translation helpful? Give feedback.
Hey @Dorian-Grim
When you're installing https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap.git#main, you gather the files from our current main branch, so
my-app/node_modules/boosted/scss/_alert.scsscontains the new stuff.However, we don't regenerate what's inside
distuntil there's a new release. So you have all the new Scss files, but when youimport "boosted/dist/css/boosted.min.css"you still get the build from v5.3.2 (without the new modifications).As a proof, you won't find any
data-bs-theme=darkinmy-app/node_modules/boosted/dist/css/boosted.css(or.min.css).I think that if you want to achieve that, you have to recompile the CSS file from the Scss files contained in
…