ephraimt

ephraimt

According to the Monaca site, it is possible to put breakpoints in source code when debugging on a device via USB.

How is this done?

Monaca does not generate source maps so there is no way to step through the original source.

Please don’t answer with “check the Chrome Dev Tools documentation”.

I know how to inspect the device in Dev Tools. The problem is that all I can see is the transpiled app bundle, not the original source.

Thank you.

Re: LocalKit Debugger Chrome Dev Tools - How to add breakpoints to source?

ephraimt

The answer is here:

https://community.onsen.io/topic/1272/how-to-override-css/2

ephraimt

OK, I figured out the answer to my question.

The solution is to require your custom css file in main.jsx. The file should be located relative to the src/ directory.

// src/main.jsx

require( "./override.css" );

// src/override.css

.tabbar--material__button .tabbar__label {
    font-size: 14px;
    font-weight: bold;
    font-family: roboto, sans-serif;
}

ephraimt

Thank you for the suggestions.

I would like to know how I can add a reference to my own .CSS file in index.html, such that it will appear after the other .CSS links in <head>.

When I add a link at the end of the head of src/public/index.html.ejs, it always gets output BEFORE the app.css link in the generated index.html file, so app.css is last like this:

… <link href=custom.css rel=stylesheet> <link href=app.css rel=stylesheet></head>

How can I insert a CSS link after app.css?

Thank you.

ephraimt

Can someone please explain simply and precisely how to override the CSS in my Monaca / React / Onsen project?

I want to be able to write CSS that will be inserted AFTER the existing CSS so that I can make specific changes to specific Onsen components.

ephraimt

Upgraded LocalKit to 2.2.1 and choosing “Upload” or “Remote Build” displays an empty Alert.

0_1490769614885_monaca-localkit-2.2.1-Remote-Build-Alert.jpg

I already tried deleting the file “local_properties.json” as per https://community.onsen.io/topic/1246/monica-localkit-2-2-0-not-working-on-windows but that did not help.

ephraimt

Thank you. That worked!

ephraimt

Since upgrading Monaca Localkit to 2.2.0, most of the features do not work. I am running Windows 7.

“Upload” shows a spinner for a long time and then shows an empty alert box.

0_1489694937322_monaca-localkit-2.2.0-Download.jpg

" Remote Build" shows a spinner for a long time and then shows an alert box with [object Object] in it.

0_1489695109583_monaca-localkit-2.2.0-Remote-Build.jpg

0_1489695124656_monaca-localkit-2.2.0-Remote-Build-Alert.jpg

Basically I can’t create debuggers or upload projects to Cloud IDE.

ephraimt

Should say “indeterminate”, not “intermediate”, in Props docs.

ephraimt

I have tried debugging my code through Monaca LocalKit Debugger and directly through Chrome DevTools (inspect) but I don’t see how I can put breakpoints in the source code.

How do I even see the original source code (App.jsx, for example)? All I can see when debugging are the compiled bundle files, such as app.bundle.js.

ephraimt

@ephraimt

Posts made by ephraimt