-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated Dockerfile can't build assets installed with npm --save
#5976
Comments
i had a similar problem like this when implementing https://schedule-x.dev/. The solution was to tell tailwindcss to generate a main.css instead of app.css and esbuild generates a new app.css because schedule-x has its own CSS and esbuild overwrites the tailwind generated app.css in such cases #5912 (comment) Steps:
|
Rather than removing Here's how it's done: I remember the reason for removing |
Environment
Actual behavior
I've installed xterm.js with
npm i @xterm/xterm --save
(straight from the phoenix docs), which placed it inassets/node_modules
as expected. When I import this in either myapp.css
orapp.js
it works as expected when running in development:When I attempt to build this with Docker, however, it fails because
.dockerignore
includes this:Expected behavior
I'd like my Dockerfile to build my assets properly when I follow the docs for adding using an npm.
The text was updated successfully, but these errors were encountered: